13 Jun
2024
13 Jun
'24
5:33 p.m.
As I've already explained, after a 4-year process, we have been approved for
governmental installation. Your so-called "policy" is causing concerns where we
actually use RF for emergencies.
- I would need to know when I need to notify organizations that this policy affect
their emergency communications plans
- I need to schedule this
- Our sponsor's approval process may be canceled anyway (i.e. your network seems to
just make arbitrary changes without even considering the infrastructure, users, usage,
DOWNTIME, etc.) - for something like DNS that usually remains untouched once set
You can just imagine other logistics particular to those points. I'm not sure if you
think people merely "play radio" or what infrastructure, but please keep in mind
people who really have concerns when you send these emails from California (or whatever
radio vacation spot foundation funds accommodate communication).
Til this date, nobody has once said when changes may actually affect the users, which I
find scary for folks who claim to work professionally in the IT field. Most times, we only
find out after issues have occurred/discovered. Why am I the only person who finds that
odd?
- KB3VWG
- KB3VWG
On Thursday, June 13, 2024 at 06:11:09 AM EDT, lleachii--- via 44net
<44net(a)mailman.ampr.org> wrote:
Chris,
I have logged in and understand that the portal system says "with user".
What I do not understand is this -
- Is there a policy in place?
- Will you then proceed to delete these "non callsign" entries once one it is
implemented?
You all may not have noticed, but I'm being very particular NOT to agree to new DNS
terms, IP record changes, etc. (i.e. stuff that preexisted your control of this domain and
space). Before I post the text (since it's quite similar to what I read posted by an
ARDC employee), I will not quote it at this time. Please offer clarity (publicly, because
you have said some derogatory things to me before in private which you seem uncourageous
to say publicly - so I'm uncomfortable) before I proceed.
I also need ARDC to understand that there will be concerns if you then proceed to delete
entries I've made very clear I wish to continue use of (as well as my GOVERNMENTAL
RACES SPONSOR). I've explained the nature of your inheritance, but somehow - I need to
clarify this seemingly contrary policy before I agree.
Please note, my records also show and indicate this "policy" is not because of
the numerous amount of DNS records - I will not discuss this further here. Anyone seeing
the updates on portal ticket clearing statistics can see that. And if your answer is YES
to the latter question above - common sense also provides that you can just as well
identify and handle them, as you would need to do so to accomplish that task. Yet, a
hassle for records I'm in fact attempting to claim (over and over - obviously I'm
making records that I'm clamming them)?
Since I pray common scene now prevails - I simply ask you not hold my records
"hostage" in this commercialization game.
Thanks and 73,
Lynwood
KB3VWG
(reviewed by a Sensitivity Expert, please be courageous and secretly report the entire
text as a Code of Conduct violation if you desire, including this disclaimer to show your
ignorance - yes this portion was reviewed as well)
On Wednesday, June 12, 2024 at 03:17:04 PM EDT, Chris via 44net
<44net(a)mailman.ampr.org> wrote:
Lynwood,
Please check your tickets, I replied 2 day ago, just waiting on your reply.
73,Chris - G1FEF
On 12 Jun 2024, at 18:43, lleachii--- via 44net <44net(a)mailman.ampr.org> wrote:
I have not been allowed to make those edits.
On Wednesday, June 12, 2024 at 01:36:45 PM EDT, Steve L via 44net
<44net(a)mailman.ampr.org> wrote:
In my opinion for the purposes of tracking ownership, nonstandard subdomains should only
exist via a cname record.
Example of Lynwood (doing it correctly in my opinion)
speedtest.ampr.org. 300 IN CNAME kb3vwg-010.ampr.org.
kb3vwg-010.ampr.org. 300 IN A 44.60.44.10
In theory speedtest.ampr.org could have a direct A record.. such asspeedtest.ampr.org.
300 IN A 44.60.44.10
But that is problematic.
Just my 2 cents.
On Wed, Jun 12, 2024 at 12:11 PM Rosy Schechter - KJ7RYV via 44net
<44net(a)mailman.ampr.org> wrote:
Dear 44Net community,
It’s been just over two months since we launched the new Portal. It came
with, as you have seen, some major bumps. Today, ARDC is resolving, at
least temporarily, one of those hurdles: administrative access to
subdomains.
As of today, anyone who had a subdomain with ampr.org before the launch
of the new Portal on April 3, 2024, will, for now, have full access to
their DNS records. This includes subdomains that fall outside of our
preferred format of callsign.ampr.org.
This administrative access still depends on call sign verification,
which requires confirming given name, family name, email, and valid
amateur radio license. This step helps us ensure that the network is
being used by valid amateur radio operators. During our recent work,
we’ve found several bad actors, which is both unfair to the community
and a security risk.
We’ve also made a functional change to the portal: once a call sign is
verified, you are now automatically able to create a subdomain with the
format of callsign.ampr.org. All other new requests for subdomains that
fall outside of that format (e.g., foo.ampr.org, which I’ll refer to as
nonstandard subdomains for brevity) will require review and approval.
Please note that we will be limiting the number of nonstandard
subdomains going forward. Thus, if you have one (or, in some cases, many
more), please consider it temporary. You can currently create as many
second-level subdomains as you want—e.g., foo.callsign.ampr.org,
bar.callsign.ampr.org, etc.
We are working on a more official policy around subdomains using
ampr.org. As promised at the recent regional coordinators' meeting, we
will ensure you can see this policy before officially implementing it.
We will also provide a transition period, likely many months, for users
to edit their entries before official deprecation. This is, ultimately,
what we should have done initially, and we take responsibility for not
following a better process and, instead, rolling out this change without
taking proper preparatory steps.
Some of you may be wondering why we are making this change in the first
place. It is because, without doing so, we end up in our current and
very unwieldy situation: a database of over 51,000 DNS entries, most
without knowledge of who they belong to, accumulated over at least a
decade, with very few entries currently in use. If we aim to increase
the usage of 44Net, then we need a system where we understand ownership
and are able to provide an efficient service where we can address
problems as they arise.
For now, we hope that this helps to unblock anyone that currently feels
blocked, while also providing an ample notice for changes that are
coming down the pipeline at a later, though likely not-so-distant date.
If you have questions, please ask.
Many thanks,
Rosy
--
Rosy Schechter - KJ7RYV
Executive Director
Amateur Radio Digital Communications (ARDC)
ardc.net
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org
_______________________________________________
44net mailing list -- 44net(a)mailman.ampr.org
To unsubscribe send an email to 44net-leave(a)mailman.ampr.org