#iana — Public Fediverse posts

@karlauerbach @tychotithonus

Cavebear wrote:

I have trouble accepting anything rooted in a country code top level domain (ccTLD), such as .me or .it, as being secure for use identifying people in the US.

Notwithstanding contemporary community constructs such as KeyOxide, there is an air of (perhaps misplaced) stability with some popular ccTLDs, like, .CA or .CO and even with some that aren't (arguably) quite so deserving, like .TV which has itself had a few turbulent hiccups for registrants in the past. The .CA ccTLD has seen it's fair share of Californian's attempting to capitalize on the mnemonics of that ccTLD, when clearly, this isn't something Canada is happy about, and indeed, one might argue that it dilutes the national branding that is beneficial to Canadian companies.

.CO is right up there near the top of the warning bells, since many believe that governments have both total authority over their ISO-3166 assets and the wisdom to manage them - they do not.

In an even earlier article penned by Kieren McCarthy, he states:

>The first thing .CO Internet did was to ignore accepted wisdom. Even now, many of those comfortable with the status quo claim that new extensions are “not needed”. They include well-known Internet figures such as Tim Berners-Lee, inventor of the World Wide Web. According to this logic, the Internet’s naming infrastructure is no more interesting than the phone system or the road network.

For my part, even back when offered tidy little sums to provide "professional valuations" for various domain names, I typically accepted the contract and disappointed the client by providing my expert assessments of $35.00 - NSI was charging $70.00 for two year registrations at the time.

Easy Peasy. The value of a domain registration is, within reason, that which the registry operator sets as the registration fee.

So with respect to Mr. McCarthy's observation, I concur with the belief that these machinations we rolled out in the 1980's as vehicles to assist humans in mapping out and arriving at particular IP addresses are certainly, nothing more than what could be arbitrary strings in a database, assigned (i.e., registered) by request to someone who will leverage it for utilitarian purposes. I know that's really dry. It's how any engineer would look at such a construct functionally.

Where things got weird was when people with marketing minds started to claim a piece of the pie, when it wasn't even sliced into pieces:

- You cannot own a domain name. It's a registration, congruent with the nature of a phone number - pay the renewal fee or that string of characters will return to the pool of available names.
- You can't assign value beyond that of the registration fees established by the registry
- If you built a brand of value tied to your (phone number or) domain registration's string, and that registration expires, the value of that brand reverts to $0.00 - once again, you cannot own a domain name, or a phone number!
- If you build a brand and register that service or trademark with the USPTO, know that it by definition exists separately from a domain registration that you do not, and cannot yourself, own.
- If you trust your brand on the two letter ccTLDs of nations, know that your brand's name recognition is subject to the whims of that nation and maybe even that nation's ever shifting political sand beneath it.

That last one is interesting when you consider that even the United States' management of the .US Top-Level Domain came under public scrutiny for the resulting calamity when the rug was pulled out from long time regional registry providers and their registrants when the geographic nature of 3LD registrations and below under the .US ccTLD were sunsetted under the management of the NTIA.

To be fair, this wasn't nearly as catastrophic as the zillions of registrants whose domain registrations were amputated following Brexit.

The .TV ccTLD has been in the news as well, scrutinized as a Top-Level domain that will potentially cease to exist, eventually. and historically, management of .TV's registry operations (and marketing) has been a never ending marathon of musical chairs. GoDaddy is actually the operator, while the Tuvalu Telecommunications Corporation handles all the sales and marketing for the brand.

Montenegro has had a tumultuous life cycle, and the reservations expressed by Karl aren't just valid, but IMO, should be taken as a literal precautionary note. Nevertheless, pigeonholed schemata persist when the marketing types slick back their hair with Brylcreem and their mouths start moving, with promises of great fortune billowing from their lips. the .ME TLD was born, if you will, from the ashes of a succession of ISO-3166 ccTLDs going back originally to Yugoslavia's .YU ccTLD.

Although I've been focusing on the ccTLDs that have attempted to brand with varying degrees of success and reliability, the smell of money attracts the same carpetbaggers to gTLDs like .mobi and .tel have had varying degrees of success as registries - with some, like the .GOO TLD outright imploding. Let's cover a few...

- .TEL - A lot of money was poured into this new age virtual business card that was supposedly only available as captive portal with pre-populated fields to fill out for your contact information. I guess that didn't work out too well, following the initial interest by curios folks, since they've officially done away with that hard requirement. Truth be told, it was always possible to simply register your own DNS servers as AUTH and completely bypass their captive portal system, and many gearheads did just to make light of what many considered redundant, ridiculous, and unnecessarily retro.
- .WORK - As if it could be the rubber banding of a wagon wheel, instead of the original steel girding that .jobs (and yes, there was a .job application too) never really delivered on, this might go down as a better 'marketed' mousetrap, but I don't get the impression that this TLD is really making many waves, and the utility is rather questionable too for anything other than very specialized cases that might be better served under one of the classic gTLDs.
- .JOBS - I was personally brought in as an expert consultant in to help get this (and .JOB, which didn't make it) accepted in a round 2 application in 2004, for acceptance into the DNS Root with ICANN, which was successful. But that's only half the battle, when job seekers actively flock to Dice, Indeed, XING, Linkedin, and one considers that the average human will at first likely guess that a site called jobs.com might be a first stop on their career search (retail.jobs forwards to usa.jobs), I don't know if the past 21 years have really bore out any fruit for this particular TLD. I was never enthusiastic about the potential, I mean, consider dog_groomer.jobs, yet I was highly optimistic that I could get them across the finish line of the acceptance process - which I did.
- .WOLTERSKLUWER - Yes that's called an Easter Egg. I've never heard of a single .wolterskluwer domain, or the TLD itself, but all I can come up with "Egads! What were you thinking?" Oh, yeah, the Easter Egg... .BOO is indeed for real. As you can see below, I checked the availability for Yogi_and_Boo.Boo, at the time of writing at least. No I did not follow through on registering but I'm sure that someone will. I still check however, occasionally, to see if Chicken.Coop is available.

The DNS Name Space is full of failed TLDS.

Getting back to having enough confidence in a TLD to base your business product (and as it follows, your "brand"), I'm going to finish this article up with a bit of a horrible potential outcome when you register a domain name in the ccTLD namespace when the government is either politically unstable, inept, or both.

This is the case of the .BZ ccTLD. the original delegation by Jon (Let's just call him IANA, because that was his pseudonym for many years until his passing) was placed in what one would surmise to be a relatively stable environment - a university.

This delegation of Authority to the TLD Manager was effected on 03 September 1991 to the University of Belize, in according with the rollout of ISO-3166-1 alpha 2 codes for each country. Nothing to see here folks, so we move along to...

The phenomenon known as the .com bubble and its contemporary, affectionately or infamously referred to as the Domain Wars, close on the heels of the Browser Wars.

Whereas the registry for the ccTLD for Belize was from 1991 primarily manually, yet competently administered (i.e., by hand), the Government of Belize saw dollar signs after Jon passed away in October of 1998 and subsequently decided to contract out marketing and registry operations to a firm by the name of Economic Solutions Inc. (ESI) in 1999. That's where I come in.

History has recorded, out of convenience sake, I suppose, that the contract between the Government of Belize and ESI was for marketing only, but that's not what the contract that ESI provided me said. They were to take over registry operations and do the marketing to compete with the new .BIZ gTLD that the nascent ICANN was going to place in the DNS root.

Since I was already operating several types of registry operations ESI wanted to contract my firm to merely expand registry operations to include the .BZ ccTLD. This was not a problem, and within a few hours had a standalone registry system operational as a prototype. Since this wasn't going to be a part of any existing registry operations I had at the time, I required money to complete a build out for production commercial operations in my data center.

This is where things began to get a little sticky, as those jokers at didn't seem to understand that I don't really care about their lofty goals, and neither myself nor my CEO at the time were going to do anything without up front compensation. we provided them with the IP addresses, etc., of the new name servers, but made it clear that this zone was not going live until we were fully funded.

It devolved into a back and forth between the Government of Belize along with ESI on one side, demanding that ICANN.... um.... IANA, rather, change the delegation in the root, and the University of Belize folks on the other, who were quite nice, amicable people.

I guess this battle between the government of Belize and "IANA" went on for a couple more years, long after I severed the relationship with ESI for not performing, and eventually, that same claim of non-performance was the basis for Belize to cancel their contract too.

Anyway, in 2001 the university spawned a new entity, University Management Limited (UML), to manage everything - including the marketing, and it's remained that way ever since. All's well that ends well. But the point is, this isn't what the government wanted, and IANA made it eventually clear that they weren't going to change the delegation for the zone to any other entity. - and this is a good thing, because governments are stupid. The university staff were more than willing to work through a coordinated smooth transition, but ultimately it was ICANN - not the government of Belize, who put their foot down when it came to operational integrity.

In closing, I'd like to point out the likely damage caused to the approximately 80,000 SLD registrants under the .EU who had their registrations revoked (of the total of more than 300,000 that were threatened), as a result of Brexit, is a good example of what could have happened, had the Government of Belize had their way, on a smaller scale, yes, but with even less regard for their existing registrants.

And that's how incompetent governments do things when you don't have technical guardrails in place to prevent them from shooting themselves in the foot.

#tallship #DNS #Registry #Registrar #Domain_Names #IANA #ccTLD

⛵

RE: https://sfba.social/users/karlauerbach/statuses/116953628070701544

@karlauerbach @tychotithonus

Cavebear wrote:

I have trouble accepting anything rooted in a country code top level domain (ccTLD), such as .me or .it, as being secure for use identifying people in the US.

Notwithstanding contemporary community constructs such as KeyOxide, there is an air of (perhaps misplaced) stability with some popular ccTLDs, like, .CA or .CO and even with some that aren't (arguably) quite so deserving, like .TV which has itself had a few turbulent hiccups for registrants in the past. The .CA ccTLD has seen it's fair share of Californian's attempting to capitalize on the mnemonics of that ccTLD, when clearly, this isn't something Canada is happy about, and indeed, one might argue that it dilutes the national branding that is beneficial to Canadian companies.

.CO is right up there near the top of the warning bells, since many believe that governments have both total authority over their ISO-3166 assets and the wisdom to manage them - they do not.

In an even earlier article penned by Kieren McCarthy, he states:

>The first thing .CO Internet did was to ignore accepted wisdom. Even now, many of those comfortable with the status quo claim that new extensions are “not needed”. They include well-known Internet figures such as Tim Berners-Lee, inventor of the World Wide Web. According to this logic, the Internet’s naming infrastructure is no more interesting than the phone system or the road network.

For my part, even back when offered tidy little sums to provide "professional valuations" for various domain names, I typically accepted the contract and disappointed the client by providing my expert assessments of $35.00 - NSI was charging $70.00 for two year registrations at the time.

Easy Peasy. The value of a domain registration is, within reason, that which the registry operator sets as the registration fee.

So with respect to Mr. McCarthy's observation, I concur with the belief that these machinations we rolled out in the 1980's as vehicles to assist humans in mapping out and arriving at particular IP addresses are certainly, nothing more than what could be arbitrary strings in a database, assigned (i.e., registered) by request to someone who will leverage it for utilitarian purposes. I know that's really dry. It's how any engineer would look at such a construct functionally.

Where things got weird was when people with marketing minds started to claim a piece of the pie, when it wasn't even sliced into pieces:

- You cannot own a domain name. It's a registration, congruent with the nature of a phone number - pay the renewal fee or that string of characters will return to the pool of available names.
- You can't assign value beyond that of the registration fees established by the registry
- If you built a brand of value tied to your (phone number or) domain registration's string, and that registration expires, the value of that brand reverts to $0.00 - once again, you cannot own a domain name, or a phone number!
- If you build a brand and register that service or trademark with the USPTO, know that it by definition exists separately from a domain registration that you do not, and cannot yourself, own.
- If you trust your brand on the two letter ccTLDs of nations, know that your brand's name recognition is subject to the whims of that nation and maybe even that nation's ever shifting political sand beneath it.

That last one is interesting when you consider that even the United States' management of the .US Top-Level Domain came under public scrutiny for the resulting calamity when the rug was pulled out from long time regional registry providers and their registrants when the geographic nature of 3LD registrations and below under the .US ccTLD were sunsetted under the management of the NTIA.

To be fair, this wasn't nearly as catastrophic as the zillions of registrants whose domain registrations were amputated following Brexit.

The .TV ccTLD has been in the news as well, scrutinized as a Top-Level domain that will potentially cease to exist, eventually. and historically, management of .TV's registry operations (and marketing) has been a never ending marathon of musical chairs. GoDaddy is actually the operator, while the Tuvalu Telecommunications Corporation handles all the sales and marketing for the brand.

Montenegro has had a tumultuous life cycle, and the reservations expressed by Karl aren't just valid, but IMO, should be taken as a literal precautionary note. Nevertheless, pigeonholed schemata persist when the marketing types slick back their hair with Brylcreem and their mouths start moving, with promises of great fortune billowing from their lips. the .ME TLD was born, if you will, from the ashes of a succession of ISO-3166 ccTLDs going back originally to Yugoslavia's .YU ccTLD.

Although I've been focusing on the ccTLDs that have attempted to brand with varying degrees of success and reliability, the smell of money attracts the same carpetbaggers to gTLDs like .mobi and .tel have had varying degrees of success as registries - with some, like the .GOO TLD outright imploding. Let's cover a few...

- .TEL - A lot of money was poured into this new age virtual business card that was supposedly only available as captive portal with pre-populated fields to fill out for your contact information. I guess that didn't work out too well, following the initial interest by curios folks, since they've officially done away with that hard requirement. Truth be told, it was always possible to simply register your own DNS servers as AUTH and completely bypass their captive portal system, and many gearheads did just to make light of what many considered redundant, ridiculous, and unnecessarily retro.
- .WORK - As if it could be the rubber banding of a wagon wheel, instead of the original steel girding that .jobs (and yes, there was a .job application too) never really delivered on, this might go down as a better 'marketed' mousetrap, but I don't get the impression that this TLD is really making many waves, and the utility is rather questionable too for anything other than very specialized cases that might be better served under one of the classic gTLDs.
- .JOBS - I was personally brought in as an expert consultant in to help get this (and .JOB, which didn't make it) accepted in a round 2 application in 2004, for acceptance into the DNS Root with ICANN, which was successful. But that's only half the battle, when job seekers actively flock to Dice, Indeed, XING, Linkedin, and one considers that the average human will at first likely guess that a site called jobs.com might be a first stop on their career search (retail.jobs forwards to usa.jobs), I don't know if the past 21 years have really bore out any fruit for this particular TLD. I was never enthusiastic about the potential, I mean, consider dog_groomer.jobs, yet I was highly optimistic that I could get them across the finish line of the acceptance process - which I did.
- .WOLTERSKLUWER - Yes that's called an Easter Egg. I've never heard of a single .wolterskluwer domain, or the TLD itself, but all I can come up with "Egads! What were you thinking?" Oh, yeah, the Easter Egg... .BOO is indeed for real. As you can see below, I checked the availability for Yogi_and_Boo.Boo, at the time of writing at least. No I did not follow through on registering but I'm sure that someone will. I still check however, occasionally, to see if Chicken.Coop is available.

The DNS Name Space is full of failed TLDS.

Getting back to having enough confidence in a TLD to base your business product (and as it follows, your "brand"), I'm going to finish this article up with a bit of a horrible potential outcome when you register a domain name in the ccTLD namespace when the government is either politically unstable, inept, or both.

This is the case of the .BZ ccTLD. the original delegation by Jon (Let's just call him IANA, because that was his pseudonym for many years until his passing) was placed in what one would surmise to be a relatively stable environment - a university.

This delegation of Authority to the TLD Manager was effected on 03 September 1991 to the University of Belize, in according with the rollout of ISO-3166-1 alpha 2 codes for each country. Nothing to see here folks, so we move along to...

The phenomenon known as the .com bubble and its contemporary, affectionately or infamously referred to as the Domain Wars, close on the heels of the Browser Wars.

Whereas the registry for the ccTLD for Belize was from 1991 primarily manually, yet competently administered (i.e., by hand), the Government of Belize saw dollar signs after Jon passed away in October of 1998 and subsequently decided to contract out marketing and registry operations to a firm by the name of Economic Solutions Inc. (ESI) in 1999. That's where I come in.

History has recorded, out of convenience sake, I suppose, that the contract between the Government of Belize and ESI was for marketing only, but that's not what the contract that ESI provided me said. They were to take over registry operations and do the marketing to compete with the new .BIZ gTLD that the nascent ICANN was going to place in the DNS root.

Since I was already operating several types of registry operations ESI wanted to contract my firm to merely expand registry operations to include the .BZ ccTLD. This was not a problem, and within a few hours had a standalone registry system operational as a prototype. Since this wasn't going to be a part of any existing registry operations I had at the time, I required money to complete a build out for production commercial operations in my data center.

This is where things began to get a little sticky, as those jokers at didn't seem to understand that I don't really care about their lofty goals, and neither myself nor my CEO at the time were going to do anything without up front compensation. we provided them with the IP addresses, etc., of the new name servers, but made it clear that this zone was not going live until we were fully funded.

It devolved into a back and forth between the Government of Belize along with ESI on one side, demanding that ICANN.... um.... IANA, rather, change the delegation in the root, and the University of Belize folks on the other, who were quite nice, amicable people.

I guess this battle between the government of Belize and "IANA" went on for a couple more years, long after I severed the relationship with ESI for not performing, and eventually, that same claim of non-performance was the basis for Belize to cancel their contract too.

Anyway, in 2001 the university spawned a new entity, University Management Limited (UML), to manage everything - including the marketing, and it's remained that way ever since. All's well that ends well. But the point is, this isn't what the government wanted, and IANA made it eventually clear that they weren't going to change the delegation for the zone to any other entity. - and this is a good thing, because governments are stupid. The university staff were more than willing to work through a coordinated smooth transition, but ultimately it was ICANN - not the government of Belize, who put their foot down when it came to operational integrity.

In closing, I'd like to point out the likely damage caused to the approximately 80,000 SLD registrants under the .EU who had their registrations revoked (of the total of more than 300,000 that were threatened), as a result of Brexit, is a good example of what could have happened, had the Government of Belize had their way, on a smaller scale, yes, but with even less regard for their existing registrants.

And that's how incompetent governments do things when you don't have technical guardrails in place to prevent them from shooting themselves in the foot.

#tallship #DNS #Registry #Registrar #Domain_Names #IANA #ccTLD

⛵

RE: https://sfba.social/users/karlauerbach/statuses/116953628070701544

@karlauerbach @tychotithonus

Cavebear wrote:

I have trouble accepting anything rooted in a country code top level domain (ccTLD), such as .me or .it, as being secure for use identifying people in the US.

Notwithstanding contemporary community constructs such as KeyOxide, there is an air of (perhaps misplaced) stability with some popular ccTLDs, like, .CA or .CO and even with some that aren't (arguably) quite so deserving, like .TV which has itself had a few turbulent hiccups for registrants in the past. The .CA ccTLD has seen it's fair share of Californian's attempting to capitalize on the mnemonics of that ccTLD, when clearly, this isn't something Canada is happy about, and indeed, one might argue that it dilutes the national branding that is beneficial to Canadian companies.

.CO is right up there near the top of the warning bells, since many believe that governments have both total authority over their ISO-3166 assets and the wisdom to manage them - they do not.

In an even earlier article penned by Kieren McCarthy, he states:

>The first thing .CO Internet did was to ignore accepted wisdom. Even now, many of those comfortable with the status quo claim that new extensions are “not needed”. They include well-known Internet figures such as Tim Berners-Lee, inventor of the World Wide Web. According to this logic, the Internet’s naming infrastructure is no more interesting than the phone system or the road network.

For my part, even back when offered tidy little sums to provide "professional valuations" for various domain names, I typically accepted the contract and disappointed the client by providing my expert assessments of $35.00 - NSI was charging $70.00 for two year registrations at the time.

Easy Peasy. The value of a domain registration is, within reason, that which the registry operator sets as the registration fee.

So with respect to Mr. McCarthy's observation, I concur with the belief that these machinations we rolled out in the 1980's as vehicles to assist humans in mapping out and arriving at particular IP addresses are certainly, nothing more than what could be arbitrary strings in a database, assigned (i.e., registered) by request to someone who will leverage it for utilitarian purposes. I know that's really dry. It's how any engineer would look at such a construct functionally.

Where things got weird was when people with marketing minds started to claim a piece of the pie, when it wasn't even sliced into pieces:

- You cannot own a domain name. It's a registration, congruent with the nature of a phone number - pay the renewal fee or that string of characters will return to the pool of available names.
- You can't assign value beyond that of the registration fees established by the registry
- If you built a brand of value tied to your (phone number or) domain registration's string, and that registration expires, the value of that brand reverts to $0.00 - once again, you cannot own a domain name, or a phone number!
- If you build a brand and register that service or trademark with the USPTO, know that it by definition exists separately from a domain registration that you do not, and cannot yourself, own.
- If you trust your brand on the two letter ccTLDs of nations, know that your brand's name recognition is subject to the whims of that nation and maybe even that nation's ever shifting political sand beneath it.

That last one is interesting when you consider that even the United States' management of the .US Top-Level Domain came under public scrutiny for the resulting calamity when the rug was pulled out from long time regional registry providers and their registrants when the geographic nature of 3LD registrations and below under the .US ccTLD were sunsetted under the management of the NTIA.

To be fair, this wasn't nearly as catastrophic as the zillions of registrants whose domain registrations were amputated following Brexit.

The .TV ccTLD has been in the news as well, scrutinized as a Top-Level domain that will potentially cease to exist, eventually. and historically, management of .TV's registry operations (and marketing) has been a never ending marathon of musical chairs. GoDaddy is actually the operator, while the Tuvalu Telecommunications Corporation handles all the sales and marketing for the brand.

Montenegro has had a tumultuous life cycle, and the reservations expressed by Karl aren't just valid, but IMO, should be taken as a literal precautionary note. Nevertheless, pigeonholed schemata persist when the marketing types slick back their hair with Brylcreem and their mouths start moving, with promises of great fortune billowing from their lips. the .ME TLD was born, if you will, from the ashes of a succession of ISO-3166 ccTLDs going back originally to Yugoslavia's .YU ccTLD.

Although I've been focusing on the ccTLDs that have attempted to brand with varying degrees of success and reliability, the smell of money attracts the same carpetbaggers to gTLDs like .mobi and .tel have had varying degrees of success as registries - with some, like the .GOO TLD outright imploding. Let's cover a few...

- .TEL - A lot of money was poured into this new age virtual business card that was supposedly only available as captive portal with pre-populated fields to fill out for your contact information. I guess that didn't work out too well, following the initial interest by curios folks, since they've officially done away with that hard requirement. Truth be told, it was always possible to simply register your own DNS servers as AUTH and completely bypass their captive portal system, and many gearheads did just to make light of what many considered redundant, ridiculous, and unnecessarily retro.
- .WORK - As if it could be the rubber banding of a wagon wheel, instead of the original steel girding that .jobs (and yes, there was a .job application too) never really delivered on, this might go down as a better 'marketed' mousetrap, but I don't get the impression that this TLD is really making many waves, and the utility is rather questionable too for anything other than very specialized cases that might be better served under one of the classic gTLDs.
- .JOBS - I was personally brought in as an expert consultant in to help get this (and .JOB, which didn't make it) accepted in a round 2 application in 2004, for acceptance into the DNS Root with ICANN, which was successful. But that's only half the battle, when job seekers actively flock to Dice, Indeed, XING, Linkedin, and one considers that the average human will at first likely guess that a site called jobs.com might be a first stop on their career search (retail.jobs forwards to usa.jobs), I don't know if the past 21 years have really bore out any fruit for this particular TLD. I was never enthusiastic about the potential, I mean, consider dog_groomer.jobs, yet I was highly optimistic that I could get them across the finish line of the acceptance process - which I did.
- .WOLTERSKLUWER - Yes that's called an Easter Egg. I've never heard of a single .wolterskluwer domain, or the TLD itself, but all I can come up with "Egads! What were you thinking?" Oh, yeah, the Easter Egg... .BOO is indeed for real. As you can see below, I checked the availability for Yogi_and_Boo.Boo, at the time of writing at least. No I did not follow through on registering but I'm sure that someone will. I still check however, occasionally, to see if Chicken.Coop is available.

The DNS Name Space is full of failed TLDS.

Getting back to having enough confidence in a TLD to base your business product (and as it follows, your "brand"), I'm going to finish this article up with a bit of a horrible potential outcome when you register a domain name in the ccTLD namespace when the government is either politically unstable, inept, or both.

This is the case of the .BZ ccTLD. the original delegation by Jon (Let's just call him IANA, because that was his pseudonym for many years until his passing) was placed in what one would surmise to be a relatively stable environment - a university.

This delegation of Authority to the TLD Manager was effected on 03 September 1991 to the University of Belize, in according with the rollout of ISO-3166-1 alpha 2 codes for each country. Nothing to see here folks, so we move along to...

The phenomenon known as the .com bubble and its contemporary, affectionately or infamously referred to as the Domain Wars, close on the heels of the Browser Wars.

Whereas the registry for the ccTLD for Belize was from 1991 primarily manually, yet competently administered (i.e., by hand), the Government of Belize saw dollar signs after Jon passed away in October of 1998 and subsequently decided to contract out marketing and registry operations to a firm by the name of Economic Solutions Inc. (ESI) in 1999. That's where I come in.

History has recorded, out of convenience sake, I suppose, that the contract between the Government of Belize and ESI was for marketing only, but that's not what the contract that ESI provided me said. They were to take over registry operations and do the marketing to compete with the new .BIZ gTLD that the nascent ICANN was going to place in the DNS root.

Since I was already operating several types of registry operations ESI wanted to contract my firm to merely expand registry operations to include the .BZ ccTLD. This was not a problem, and within a few hours had a standalone registry system operational as a prototype. Since this wasn't going to be a part of any existing registry operations I had at the time, I required money to complete a build out for production commercial operations in my data center.

This is where things began to get a little sticky, as those jokers at didn't seem to understand that I don't really care about their lofty goals, and neither myself nor my CEO at the time were going to do anything without up front compensation. we provided them with the IP addresses, etc., of the new name servers, but made it clear that this zone was not going live until we were fully funded.

It devolved into a back and forth between the Government of Belize along with ESI on one side, demanding that ICANN.... um.... IANA, rather, change the delegation in the root, and the University of Belize folks on the other, who were quite nice, amicable people.

I guess this battle between the government of Belize and "IANA" went on for a couple more years, long after I severed the relationship with ESI for not performing, and eventually, that same claim of non-performance was the basis for Belize to cancel their contract too.

Anyway, in 2001 the university spawned a new entity, University Management Limited (UML), to manage everything - including the marketing, and it's remained that way ever since. All's well that ends well. But the point is, this isn't what the government wanted, and IANA made it eventually clear that they weren't going to change the delegation for the zone to any other entity. - and this is a good thing, because governments are stupid. The university staff were more than willing to work through a coordinated smooth transition, but ultimately it was ICANN - not the government of Belize, who put their foot down when it came to operational integrity.

In closing, I'd like to point out the likely damage caused to the approximately 80,000 SLD registrants under the .EU who had their registrations revoked (of the total of more than 300,000 that were threatened), as a result of Brexit, is a good example of what could have happened, had the Government of Belize had their way, on a smaller scale, yes, but with even less regard for their existing registrants.

And that's how incompetent governments do things when you don't have technical guardrails in place to prevent them from shooting themselves in the foot.

#tallship #DNS #Registry #Registrar #Domain_Names #IANA #ccTLD

⛵

RE: https://sfba.social/users/karlauerbach/statuses/116953628070701544

I think that rel="sitemap" ought to be in the IANA Link Relations registry.

More details at:

https://github.com/protocol-registries/link-relations/issues/72

#IANA #Standards #WebDev #SemanticWeb #HTML

I think that rel="sitemap" ought to be in the IANA Link Relations registry.

More details at:

https://github.com/protocol-registries/link-relations/issues/72

#IANA #Standards #WebDev #SemanticWeb #HTML

I think that rel="sitemap" ought to be in the IANA Link Relations registry.

More details at:

https://github.com/protocol-registries/link-relations/issues/72

#IANA #Standards #WebDev #SemanticWeb #HTML

I think that rel="sitemap" ought to be in the IANA Link Relations registry.

More details at:

https://github.com/protocol-registries/link-relations/issues/72

#IANA #Standards #WebDev #SemanticWeb #HTML

I think that rel="sitemap" ought to be in the IANA Link Relations registry.

More details at:

https://github.com/protocol-registries/link-relations/issues/72

#IANA #Standards #WebDev #SemanticWeb #HTML

Oh, hey, #IANA assigned a new block of ASNs to #AFRINIC. A good sign that the #Internet #connectivity in #Africa is growing! Keep up the good work! Details here....

#ASN #BGP

Oh, hey, #IANA assigned a new block of ASNs to #AFRINIC. A good sign that the #Internet #connectivity in #Africa is growing! Keep up the good work! Details here....

#ASN #BGP

Oh, hey, #IANA assigned a new block of ASNs to #AFRINIC. A good sign that the #Internet #connectivity in #Africa is growing! Keep up the good work! Details here....

#ASN #BGP

Oh, hey, #IANA assigned a new block of ASNs to #AFRINIC. A good sign that the #Internet #connectivity in #Africa is growing! Keep up the good work! Details here....

#ASN #BGP

Just scraping the #IANA assigned TLDs and the corresponding documented #nameservers. What I don't get is, why so many companies apply for a #TLD. It's not particularly cheap to apply for one of those ngTLDs, yet compared to the company sizes, it's probably pennies. Is it a prestige investment? Is it a digital resource to grab, before someone else does it?

Other than #Microsoft, #Google, and #AWS, I've rarely seen any ngTLD representing a corporation's name to actually be used in practice.

Does anyone in the #infosec community share their view?

#askfedi #askmasto #askinfosec #DNS

Just scraping the #IANA assigned TLDs and the corresponding documented #nameservers. What I don't get is, why so many companies apply for a #TLD. It's not particularly cheap to apply for one of those ngTLDs, yet compared to the company sizes, it's probably pennies. Is it a prestige investment? Is it a digital resource to grab, before someone else does it?

Other than #Microsoft, #Google, and #AWS, I've rarely seen any ngTLD representing a corporation's name to actually be used in practice.

Does anyone in the #infosec community share their view?

#askfedi #askmasto #askinfosec #DNS

Just scraping the #IANA assigned TLDs and the corresponding documented #nameservers. What I don't get is, why so many companies apply for a #TLD. It's not particularly cheap to apply for one of those ngTLDs, yet compared to the company sizes, it's probably pennies. Is it a prestige investment? Is it a digital resource to grab, before someone else does it?

Other than #Microsoft, #Google, and #AWS, I've rarely seen any ngTLD representing a corporation's name to actually be used in practice.

Does anyone in the #infosec community share their view?

#askfedi #askmasto #askinfosec #DNS

Just scraping the #IANA assigned TLDs and the corresponding documented #nameservers. What I don't get is, why so many companies apply for a #TLD. It's not particularly cheap to apply for one of those ngTLDs, yet compared to the company sizes, it's probably pennies. Is it a prestige investment? Is it a digital resource to grab, before someone else does it?

Other than #Microsoft, #Google, and #AWS, I've rarely seen any ngTLD representing a corporation's name to actually be used in practice.

Does anyone in the #infosec community share their view?

#askfedi #askmasto #askinfosec #DNS

Just scraping the #IANA assigned TLDs and the corresponding documented #nameservers. What I don't get is, why so many companies apply for a #TLD. It's not particularly cheap to apply for one of those ngTLDs, yet compared to the company sizes, it's probably pennies. Is it a prestige investment? Is it a digital resource to grab, before someone else does it?

Other than #Microsoft, #Google, and #AWS, I've rarely seen any ngTLD representing a corporation's name to actually be used in practice.

Does anyone in the #infosec community share their view?

#askfedi #askmasto #askinfosec #DNS

RE: https://chaos.social/@joergi/115594789795742237

Please answer if you know about TLDs/IANA:

if you really wanna #unplugtrump and don't want to have a domain in the US for anti-censorship:
if you look at https://www.iana.org/domains/root/db/chanel.html
the Sponsoring Organisation & Administrative Contact are in the EU, which is good
but the Technical Contact is in the US.

So is it then really save? and: the complete IANA /ICANN are in the US - so does it matter at all?

#trump #sovereignty #digitalsovereignty #digitalAutonomy #tld #domain #domains #iana #ICANN

RE: https://chaos.social/@joergi/115594789795742237

Please answer if you know about TLDs/IANA:

if you really wanna #unplugtrump and don't want to have a domain in the US for anti-censorship:
if you look at https://www.iana.org/domains/root/db/chanel.html
the Sponsoring Organisation & Administrative Contact are in the EU, which is good
but the Technical Contact is in the US.

So is it then really save? and: the complete IANA /ICANN are in the US - so does it matter at all?

#trump #sovereignty #digitalsovereignty #digitalAutonomy #tld #domain #domains #iana #ICANN

RE: https://chaos.social/@joergi/115594789795742237

Please answer if you know about TLDs/IANA:

if you really wanna #unplugtrump and don't want to have a domain in the US for anti-censorship:
if you look at https://www.iana.org/domains/root/db/chanel.html
the Sponsoring Organisation & Administrative Contact are in the EU, which is good
but the Technical Contact is in the US.

So is it then really save? and: the complete IANA /ICANN are in the US - so does it matter at all?

#trump #sovereignty #digitalsovereignty #digitalAutonomy #tld #domain #domains #iana #ICANN

RE: https://chaos.social/@joergi/115594789795742237

Please answer if you know about TLDs/IANA:

if you really wanna #unplugtrump and don't want to have a domain in the US for anti-censorship:
if you look at https://www.iana.org/domains/root/db/chanel.html
the Sponsoring Organisation & Administrative Contact are in the EU, which is good
but the Technical Contact is in the US.

So is it then really save? and: the complete IANA /ICANN are in the US - so does it matter at all?

#trump #sovereignty #digitalsovereignty #digitalAutonomy #tld #domain #domains #iana #ICANN

RE: https://chaos.social/@joergi/115594789795742237

Please answer if you know about TLDs/IANA:

if you really wanna #unplugtrump and don't want to have a domain in the US for anti-censorship:
if you look at https://www.iana.org/domains/root/db/chanel.html
the Sponsoring Organisation & Administrative Contact are in the EU, which is good
but the Technical Contact is in the US.

So is it then really save? and: the complete IANA /ICANN are in the US - so does it matter at all?

#trump #sovereignty #digitalsovereignty #digitalAutonomy #tld #domain #domains #iana #ICANN

We’ve formally requested #ICANN and #IANA to redelegate Yemen’s .YE domain.

Why? Because it’s hijacked by a militia and abused for:
🔴 Propaganda
🔴 Censorship
🔴 Repression

📄 Full letter: https://freethedotye.org/letter

#FreeDotYE #Yemen #DigitalRights #DNS #InternetFreedom #HumanRights

We’ve formally requested #ICANN and #IANA to redelegate Yemen’s .YE domain.

Why? Because it’s hijacked by a militia and abused for:
🔴 Propaganda
🔴 Censorship
🔴 Repression

📄 Full letter: https://freethedotye.org/letter

#FreeDotYE #Yemen #DigitalRights #DNS #InternetFreedom #HumanRights

We’ve formally requested #ICANN and #IANA to redelegate Yemen’s .YE domain.

Why? Because it’s hijacked by a militia and abused for:
🔴 Propaganda
🔴 Censorship
🔴 Repression

📄 Full letter: https://freethedotye.org/letter

#FreeDotYE #Yemen #DigitalRights #DNS #InternetFreedom #HumanRights

We’ve formally requested #ICANN and #IANA to redelegate Yemen’s .YE domain.

Why? Because it’s hijacked by a militia and abused for:
🔴 Propaganda
🔴 Censorship
🔴 Repression

📄 Full letter: https://freethedotye.org/letter

#FreeDotYE #Yemen #DigitalRights #DNS #InternetFreedom #HumanRights

@cwebber @aud
Seems like an interesting idea, but I guess I'm missing something: who administers the root namespace? Or if it's rootless, how do you bootstrap a new device onto the network the first time it tries to resolve a name?

If I sound skeptical, it's not lack of interest but because there's been a lot of research and work on this area over the past several decades, e.g. by CNRI on the Handle System, or California Digital Library on ARK, and neither of them have cracked the problem of needing a social organization, at least to run the very top level of the namespace.

(Personally, I'd be pretty happy if we somehow replaced ICANN/DNS with the consortium of libraries that's behind ARK Alliance; I trust them more than I trust Verisign, certainly. But it's a low bar.)
#DNS #ICANN #IANA #HandleSystem

@cwebber @aud
Seems like an interesting idea, but I guess I'm missing something: who administers the root namespace? Or if it's rootless, how do you bootstrap a new device onto the network the first time it tries to resolve a name?

If I sound skeptical, it's not lack of interest but because there's been a lot of research and work on this area over the past several decades, e.g. by CNRI on the Handle System, or California Digital Library on ARK, and neither of them have cracked the problem of needing a social organization, at least to run the very top level of the namespace.

(Personally, I'd be pretty happy if we somehow replaced ICANN/DNS with the consortium of libraries that's behind ARK Alliance; I trust them more than I trust Verisign, certainly. But it's a low bar.)
#DNS #ICANN #IANA #HandleSystem

@cwebber @aud
Seems like an interesting idea, but I guess I'm missing something: who administers the root namespace? Or if it's rootless, how do you bootstrap a new device onto the network the first time it tries to resolve a name?

If I sound skeptical, it's not lack of interest but because there's been a lot of research and work on this area over the past several decades, e.g. by CNRI on the Handle System, or California Digital Library on ARK, and neither of them have cracked the problem of needing a social organization, at least to run the very top level of the namespace.

(Personally, I'd be pretty happy if we somehow replaced ICANN/DNS with the consortium of libraries that's behind ARK Alliance; I trust them more than I trust Verisign, certainly. But it's a low bar.)
#DNS #ICANN #IANA #HandleSystem

Why is Via Rail using a legitimate, owned domain name as part of their example email!!!

Domain Name: company.com
Registry Domain ID: 5202_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2025-05-27T17:21:37Z
Creation Date: 1994-07-07T23:00:00Z

AAAAAAAAAA

#viarail #canada #email #iana #cira

Why is Via Rail using a legitimate, owned domain name as part of their example email!!!

Domain Name: company.com
Registry Domain ID: 5202_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2025-05-27T17:21:37Z
Creation Date: 1994-07-07T23:00:00Z

AAAAAAAAAA

#viarail #canada #email #iana #cira

Why is Via Rail using a legitimate, owned domain name as part of their example email!!!

Domain Name: company.com
Registry Domain ID: 5202_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2025-05-27T17:21:37Z
Creation Date: 1994-07-07T23:00:00Z

AAAAAAAAAA

#viarail #canada #email #iana #cira

Why is Via Rail using a legitimate, owned domain name as part of their example email!!!

Domain Name: company.com
Registry Domain ID: 5202_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2025-05-27T17:21:37Z
Creation Date: 1994-07-07T23:00:00Z

AAAAAAAAAA

#viarail #canada #email #iana #cira

Why is Via Rail using a legitimate, owned domain name as part of their example email!!!

Domain Name: company.com
Registry Domain ID: 5202_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.godaddy.com
Registrar URL: https://www.godaddy.com
Updated Date: 2025-05-27T17:21:37Z
Creation Date: 1994-07-07T23:00:00Z

AAAAAAAAAA

#viarail #canada #email #iana #cira

Idly scrolling through /etc/services today, I am struck not only by how many ports are going to be squatted on effectively forever by unavailable commercial products from companies that no longer exist, but how many ways, both covert and overt, there are of getting a machine to tell you what it thinks that its (sometimes intranet/LAN) name is and what its system clock reads.

I also expect that utcd, unixtime, and timed will still be assigned numbers in 2039.

#infosec #IANA

Idly scrolling through /etc/services today, I am struck not only by how many ports are going to be squatted on effectively forever by unavailable commercial products from companies that no longer exist, but how many ways, both covert and overt, there are of getting a machine to tell you what it thinks that its (sometimes intranet/LAN) name is and what its system clock reads.

I also expect that utcd, unixtime, and timed will still be assigned numbers in 2039.

#infosec #IANA

Idly scrolling through /etc/services today, I am struck not only by how many ports are going to be squatted on effectively forever by unavailable commercial products from companies that no longer exist, but how many ways, both covert and overt, there are of getting a machine to tell you what it thinks that its (sometimes intranet/LAN) name is and what its system clock reads.

I also expect that utcd, unixtime, and timed will still be assigned numbers in 2039.

#infosec #IANA

Idly scrolling through /etc/services today, I am struck not only by how many ports are going to be squatted on effectively forever by unavailable commercial products from companies that no longer exist, but how many ways, both covert and overt, there are of getting a machine to tell you what it thinks that its (sometimes intranet/LAN) name is and what its system clock reads.

I also expect that utcd, unixtime, and timed will still be assigned numbers in 2039.

#infosec #IANA

Idly scrolling through /etc/services today, I am struck not only by how many ports are going to be squatted on effectively forever by unavailable commercial products from companies that no longer exist, but how many ways, both covert and overt, there are of getting a machine to tell you what it thinks that its (sometimes intranet/LAN) name is and what its system clock reads.

I also expect that utcd, unixtime, and timed will still be assigned numbers in 2039.

#infosec #IANA

Things we should just be more appreciative of: the guys maintaining the timezone database that is used in almost any piece of software … #PaulEggert #ArthurDavidOlson #tzDatabase #InternetHeroes #IANA

https://en.wikipedia.org/wiki/Tz_database

Things we should just be more appreciative of: the guys maintaining the timezone database that is used in almost any piece of software … #PaulEggert #ArthurDavidOlson #tzDatabase #InternetHeroes #IANA

https://en.wikipedia.org/wiki/Tz_database

Things we should just be more appreciative of: the guys maintaining the timezone database that is used in almost any piece of software … #PaulEggert #ArthurDavidOlson #tzDatabase #InternetHeroes #IANA

https://en.wikipedia.org/wiki/Tz_database

Things we should just be more appreciative of: the guys maintaining the timezone database that is used in almost any piece of software … #PaulEggert #ArthurDavidOlson #tzDatabase #InternetHeroes #IANA

https://en.wikipedia.org/wiki/Tz_database

At work we had to specify some date to be in Faroese timezone, and we wondered what the difference between Atlantic/Faeroe and Atlantic/Faroe (in the #tz database) was. Wikipedia revealed that Atlantic/Faeroe simply links back to Atlantic/Faroe

Now my curiosity was peaked and I wanted to know why

Thanks to the open nature of internet standards, I could just look up the #IANA's mailing list for tz

Which led me to this discussion: https://lists.iana.org/hyperkitty/list/[email protected]/thread/ZIJ75VG44WLDYUWSKWJIJ3CM3WIUMQW7/

Which revealed that it was a odd quirk

heise+ | Gemeinnütziges Web: Nonprofit-Organisationen als Gestalter der digitalen Welt

Wir geben einen Überblick über gemeinnützige Institutionen, die maßgeblich an der Entwicklung und inhaltlichen Gestaltung des Webs beteiligt sind.

https://www.heise.de/hintergrund/Gemeinnuetziges-Web-Nonprofit-Organisationen-als-Gestalter-der-digitalen-Welt-10341287.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ApacheSoftwareFoundation #FreeSoftwareFoundation #IANA #ICANN #IETF #Internet #IT #LinuxFoundation #Mozilla #WC #Wikimedia #news

heise+ | Gemeinnütziges Web: Nonprofit-Organisationen als Gestalter der digitalen Welt

Wir geben einen Überblick über gemeinnützige Institutionen, die maßgeblich an der Entwicklung und inhaltlichen Gestaltung des Webs beteiligt sind.

https://www.heise.de/hintergrund/Gemeinnuetziges-Web-Nonprofit-Organisationen-als-Gestalter-der-digitalen-Welt-10341287.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ApacheSoftwareFoundation #FreeSoftwareFoundation #IANA #ICANN #IETF #Internet #IT #LinuxFoundation #Mozilla #WC #Wikimedia #news

heise+ | Gemeinnütziges Web: Nonprofit-Organisationen als Gestalter der digitalen Welt

Wir geben einen Überblick über gemeinnützige Institutionen, die maßgeblich an der Entwicklung und inhaltlichen Gestaltung des Webs beteiligt sind.

https://www.heise.de/hintergrund/Gemeinnuetziges-Web-Nonprofit-Organisationen-als-Gestalter-der-digitalen-Welt-10341287.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ApacheSoftwareFoundation #FreeSoftwareFoundation #IANA #ICANN #IETF #Internet #IT #LinuxFoundation #Mozilla #WC #Wikimedia #news

heise+ | Gemeinnütziges Web: Nonprofit-Organisationen als Gestalter der digitalen Welt

Wir geben einen Überblick über gemeinnützige Institutionen, die maßgeblich an der Entwicklung und inhaltlichen Gestaltung des Webs beteiligt sind.

https://www.heise.de/hintergrund/Gemeinnuetziges-Web-Nonprofit-Organisationen-als-Gestalter-der-digitalen-Welt-10341287.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ApacheSoftwareFoundation #FreeSoftwareFoundation #IANA #ICANN #IETF #Internet #IT #LinuxFoundation #Mozilla #WC #Wikimedia #news

heise+ | Gemeinnütziges Web: Nonprofit-Organisationen als Gestalter der digitalen Welt

Wir geben einen Überblick über gemeinnützige Institutionen, die maßgeblich an der Entwicklung und inhaltlichen Gestaltung des Webs beteiligt sind.

https://www.heise.de/hintergrund/Gemeinnuetziges-Web-Nonprofit-Organisationen-als-Gestalter-der-digitalen-Welt-10341287.html?wt_mc=sm.red.ho.mastodon.mastodon.md_beitraege.md_beitraege&utm_source=mastodon

#ApacheSoftwareFoundation #FreeSoftwareFoundation #IANA #ICANN #IETF #Internet #IT #LinuxFoundation #Mozilla #WC #Wikimedia #news

Interesting final note:

#FreeBSD/#NetBSD (and netkit-rwho) #rwhod uses the original "who" UDP port, 513.

There's a "new-who" UDP+TCP port, 550 and a "new" 224.0.2.1 multicast address. They have been in the assigned number list ever since RFC 1090, footnoted to Jon Postel and the "unofficial" BSD "rwho Group".

They've been reserved for 35 years, and I can find nothing to show for the efforts of whatever this "unofficial Group" was.

#AssignedNumbers #IANA