Julian De Marchi | 1 Oct 2008 13:47
Picon

[opennic-discuss] VOTE: Micro TLD

Voting has been motioned on the new TLD .micro

You may see the charter written by SumpLand a while ago at:
  http://wiki.opennic.glue/MicroTLD

Vote;

Yes - to accept .micro and its charter
No - to reject .micro and its charter

Voting will begin October 3, 2008 UTC, and end on October 10, 2008
UTC after 48 hours of inactive voting. Results will be posted to this
mailing list.

Note:

Ensure you are registered on http://www.opennic.glue so you can vote.
On the 3rd the voting section will appear on http://www.opennic.glue
down the bottom left section in the menu bar. Please remember to vote!
-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.

sumpland | 3 Oct 2008 23:41

Re: [opennic-discuss] VOTE: Micro TLD


i vote yes


-----Original Message-----
From: Julian De Marchi <julian <at> jdcomputers.com.au>
To: OpenNIC discussion <discuss <at> lists.opennicproject.org>
Sent: Wed, 1 Oct 2008 7:47 am
Subject: [opennic-discuss] VOTE: Micro TLD

Voting has been motioned on the new TLD .micro You may see the charter written by SumpLand a while ago at: http://wiki.opennic.glue/MicroTLD Vote; Yes - to accept .micro and its charter No - to reject .micro and its charter Voting will begin October 3, 2008 UTC, and end on October 10, 2008 UTC after 48 hours of inactive voting. Results will be posted to this mailing list. Note: Ensure you are registered on http://www.opennic.glue so you can vote. On the 3rd the voting section will appear on http://www.opennic.glue down the bottom left section in the menu bar. Please remember to vote! - To unsubscribe, email majordomo <at> lists.opennicproject.org with the words "unsubscribe discuss" in the body of the message.
Julian De Marchi | 6 Oct 2008 01:02
Picon

Re: [opennic-discuss] VOTE: Micro TLD

Julian De Marchi wrote:
> Voting has been motioned on the new TLD .micro
> 
> You may see the charter written by SumpLand a while ago at:
>   http://wiki.opennic.glue/MicroTLD
> 
> Vote;
> 
> Yes - to accept .micro and its charter
> No - to reject .micro and its charter
> 
> Voting will begin October 3, 2008 UTC, and end on October 10, 2008
> UTC after 48 hours of inactive voting. Results will be posted to this
> mailing list.
> 
> Note:
> 
> Ensure you are registered on http://www.opennic.glue so you can vote.
> On the 3rd the voting section will appear on http://www.opennic.glue
> down the bottom left section in the menu bar. Please remember to vote!

voting is now active on the website (http://www.opennic.glue)

Sorry for the lateness of the vote appearing, I feel sick on the 
weekend and only got a chance to do it now.

--

-- 
Cheers,
Julian De Marchi
--
OpenNIC user - http://www.opennicproject.org/ | http://www.opennic.glue
Support OpenNIC, become a member today!
--
http://www.geek - Secure you domain!
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.

Julian De Marchi | 10 Oct 2008 02:28
Picon

[opennic-discuss] ICANN News Alert -- Proposal To Sign the Root Zone Made Public


ICANN News Alert
http://www.icann.org/en/announcements/announcement-2-09oct08-en.htm

________________________________

Proposal To Sign the Root Zone Made Public
9 October 2008

A proposal
http://www.icann.org/en/announcements/dnssec-proposal-09oct08-en.pdf
[PDF, 276K] to sign the root zone file with Domain Name System
Security Extensions, or DNSSEC, technology was released by ICANN today.

DNSSEC provides a way for software to validate that Domain Name System
(DNS) data have not been modified during Internet transit. This is
done by incorporating public-private signature key pairs into the DNS
hierarchy to form a chain of trust originating at the root zone.
Importantly, DNSSEC is not a form of encryption.  It is backward
compatible with existing DNS, leaving records as they are –
unencrypted.  DNSSEC ensures record integrity through the use of
digital signatures that attest to their authenticity.

This proposal has been written by ICANN staff, as authorized by
ICANN's Board, with the goal to proceed with appropriate speed and
deploy DNSSEC at the root level as a step towards improving the
overall security of the DNS.

"The proposal has already been reviewed by a group of global DNSSEC
experts. The feedback ICANN received from this group indicates that
the proposal is technically sound, and appropriate" ICANN's President
and CEO Paul Twomey said.

At the core of DNSSEC is the concept of a 'chain of trust'. ICANN's
proposal builds on that notion and, based on security advice,
recommends that the entity responsible for making changes, additions
and deletions to the root zone file and confirming those changes are
valid (ICANN presently performs this function – called the IANA
function - under contract from the United States Department of
Commerce), should generate and digitally sign the resulting root zone
file update. This signed file should then be passed to another
organization (presently VeriSign Corporation) for distribution.  In
other words, the organization responsible for the initial basis of
trust - validating root zone changes with top level domain operators -
should also authenticate the validity of the final product before it
is distributed.

The release occurs as the United States Department of Commerce also
announced a Notice of Inquiry on the concept of signing the Root Zone.
Details can be found here:
http://edocket.access.gpo.gov/2008/pdf/E8-23974.pdf [PDF, 72K].

"ICANN has more than a year of experience in producing a signed root
zone that has already been widely tested by DNS software vendors and
the interested DNSSEC community. ICANN also has "built-in" the
participation of a group of world-class DNS experts" Dr Twomey said.

"This is a moment of challenge and opportunity in addressing the
overall stability and security of the DNS system - the mission around
which ICANN was formed" he added.

A set of questions and answers
http://www.icann.org/en/announcements/dnssec-qaa-09oct08-en.htm on
what DNSSEC is and why it is important is also published to assist
with the reading of the proposal.

About ICANN:

To reach another person on the Internet you have to type an address
into your computer - a name or a number. That address has to be unique
so computers know where to find each other. ICANN coordinates these
unique identifiers across the world. Without that coordination we
wouldn't have one global Internet. ICANN is responsible for the global
coordination of the Internet's system of unique identifiers like
domain names (like .org, .museum and country codes like .uk) and the
addresses used in a variety of Internet protocols that help computers
reach each other over the Internet.

ICANN was formed in 1998. It is a not-for-profit public-benefit
corporation from all over the world dedicated to keeping the Internet
secure, stable and interoperable. It promotes competition and develops
policy on the Internet's unique identifiers.

ICANN doesn't control content on the Internet. It cannot stop spam and
it doesn't deal with access to the Internet. But through its
coordination role of the Internet's naming system, it does have an
important impact on the expansion and evolution of the Internet.

Media Contact:

Jason Keenan
Media Advisor, ICANN
P: +1 310 382 4004
E: jason.keenan <at> icann.org

________________________________

Sign up for ICANN's Monthly Magazine http://www.icann.org/magazine/

This message was sent by: ICANN, 4676 Admiralty Way, Suite 330
, Marina del Rey, CA 90292-6601

Powered by iContact: http://freetrial.icontact.com

Manage your subscription:
http://app.icontact.com/icp/mmail-mprofile.pl?r=10094651&l=6333&s=401Q&m=183857&c=165637

--
Cheers,
Julian De Marchi
--
OpenNIC user - http://www.opennicproject.org/ | http://www.opennic.glue
Support OpenNIC, become a member today!
--
http://www.geek - Secure you domain!
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
Tim Groeneveld | 10 Oct 2008 07:47

Re: [opennic-discuss] ICANN News Alert -- Proposal To Sign the Root Zone Made Public

On Friday 10 October 2008 10:28:43 am Julian De Marchi wrote:
> DNSSEC provides a way for software to validate that Domain Name System
> (DNS) data have not been modified during Internet transit. This is
> done by incorporating public-private signature key pairs into the DNS
> hierarchy to form a chain of trust originating at the root zone.
> Importantly, DNSSEC is not a form of encryption.  It is backward
> compatible with existing DNS, leaving records as they are –
> unencrypted.  DNSSEC ensures record integrity through the use of
> digital signatures that attest to their authenticity.

How long would it be until OpenNIC would be able to integrate such technology? 
IIRC, BIND supports DNSSEC.

But in the end, does it __really__ matter if we don't have it? I suppose soon 
things like online banking apps may start wanting to ensure DNSSEC records 
exist, so they know that they are contacting the right machines, etc.

But that shouldn't really matter, anyways, as most online banking apps are web 
based and use SSL.

To be honest, DNSSEC seems like a lot of overhead for not much benifit.

  - Tim
Julian De Marchi | 10 Oct 2008 14:19
Picon

Re: [opennic-discuss] ICANN News Alert -- Proposal To Sign the Root Zone Made Public

> How long would it be until OpenNIC would be able to integrate such technology? 
> IIRC, BIND supports DNSSEC.

This topic has not really been discussed before. The free TLD has
proved it will work however.

> But in the end, does it __really__ matter if we don't have it? I suppose soon 
> things like online banking apps may start wanting to ensure DNSSEC records 
> exist, so they know that they are contacting the right machines, etc.

For us, we have our DNS records open anyway, so anyone can grab them.
If our polices change, and we close our zones from being able to be
transfered by anyone, then maybe it might help. So to answer you
questions, I do not think it really matters if we don't use it at this
point in time.

> To be honest, DNSSEC seems like a lot of overhead for not much benifit.

I use DNSSEC, and have not noticed a slow down in zone times. If you
would like to test, the free zone on ns21.opennic.glue is using it.

--julian
-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.

Bret Lang | 10 Oct 2008 15:23
Picon

Re: [opennic-discuss] ICANN News Alert -- Proposal To Sign the Root Zone Made Public

I think we could all be lossing sight on the bigger picture.  While this seems harmless
it signals a scary grab for power and control by ICCAN and corporate America.
 
Lets say ICCAN and Microsoft teamed up and built this directly into the browser they
would overnight take over 89% market share of the web!  Completly blocking 3rd party players like OpenNIC
 
As it stands now anyone can set DNS info, but think what would happen if DNSSEC handshakes become hardcoded in the browser, even if we duplicated the function here
at OpenNIC it wouldn't handshake here...
 
This is why I believe Google has wasted so much money developing Chrome, there hedging there bets against this type of end run.
 
So I'd say before we spend alot of time incorporating this technology we find out more
about the public-private signature key pairs and where those will be housed or validated through!
 
If the keys handshake the transaction thats fine, but if the keys handshake the originating root servers well then we are one step closer to big brother.

 
On 10/10/08, Tim Groeneveld <tim <at> timg.ws> wrote:
On Friday 10 October 2008 10:28:43 am Julian De Marchi wrote:
> DNSSEC provides a way for software to validate that Domain Name System
> (DNS) data have not been modified during Internet transit. This is
> done by incorporating public-private signature key pairs into the DNS
> hierarchy to form a chain of trust originating at the root zone.
> Importantly, DNSSEC is not a form of encryption.  It is backward
> compatible with existing DNS, leaving records as they are –
> unencrypted.  DNSSEC ensures record integrity through the use of
> digital signatures that attest to their authenticity.

How long would it be until OpenNIC would be able to integrate such technology?
IIRC, BIND supports DNSSEC.

But in the end, does it __really__ matter if we don't have it? I suppose soon
things like online banking apps may start wanting to ensure DNSSEC records
exist, so they know that they are contacting the right machines, etc.

But that shouldn't really matter, anyways, as most online banking apps are web
based and use SSL.

To be honest, DNSSEC seems like a lot of overhead for not much benifit.

- Tim


Julian De Marchi | 13 Oct 2008 13:28
Picon

Re: [opennic-discuss] VOTE: Micro TLD


Julian De Marchi wrote:
> Voting has been motioned on the new TLD .micro
> 
> You may see the charter written by SumpLand a while ago at:
>   http://wiki.opennic.glue/MicroTLD
> 
> Vote;
> 
> Yes - to accept .micro and its charter
> No - to reject .micro and its charter

Voting has officially ended. Micro has been voted in by 6 votes.

Tim; please get the server setup, then contact me.

--julian

Julian De Marchi | 15 Oct 2008 06:19
Picon

[opennic-discuss] dns operations


Hey Guys,

There is a new mailing list active for OpenNIC.
dns-operations <at> lists.opennicproject.org.

This list is used for Nagios alerts for the OpenNIC namespace. Only
zone issues are sent to the list, host issues are sent to the
respective server admin. I imagine this list will be high in volume,
as if a zone is broken, Nagios will send alerts every hour. This is
there so that the admin is pestered enough to get the issue fixed.

This list hopefully will mature into a place to have discussions about
the dns operations of OpenNIC. The list is not closed, and is open to
every OpenNIC member.

to subscribe send an email to;

majordomo <at> lists.opennicproject.org

with subscribe dns-operations in the body of the email.

Any questions?

--
Cheers,
Julian De Marchi
--
OpenNIC user - http://www.opennicproject.org/ | http://www.opennic.glue
Support OpenNIC, become a member today!
--
http://www.geek - Secure you domain!
--
Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html
Jacob Bachmeyer | 19 Oct 2008 20:45
Picon

Re: [opennic-discuss] ICANN News Alert -- Proposal To Sign the Root Zone Made Public


>> How long would it be until OpenNIC would be able to integrate such technology? 
>> IIRC, BIND supports DNSSEC.
>>     
>
> This topic has not really been discussed before. The free TLD has
> proved it will work however.
>   
I suggested signing the OpenNIC root back in July. You are right that 
there was not much discussion about it though.
>> But in the end, does it __really__ matter if we don't have it? I suppose soon 
>> things like online banking apps may start wanting to ensure DNSSEC records 
>> exist, so they know that they are contacting the right machines, etc.
>>     
>
> For us, we have our DNS records open anyway, so anyone can grab them.
> If our polices change, and we close our zones from being able to be
> transfered by anyone, then maybe it might help. So to answer you
> questions, I do not think it really matters if we don't use it at this
> point in time.
>   

One of the characteristics of cryptographic signatures is that a signed 
document can be passed around and the signature remains valid if and 
only if the document is not modified.

Why should it matter if anyone can copy the signed zone, since modifying 
it would invalidate the signature?  So it would still be "the OpenNIC 
root zone" no matter who is handing it out.

> --julian
--jacob
-
To unsubscribe, email majordomo <at> lists.opennicproject.org with the words
"unsubscribe discuss" in the body of the message.


Gmane