Thursday, March 19, 2009

Privatization vs Nationalization

Thesis:

    Governments should not implement DNS-SEC on
    public infrastructure. Instead, individual
    private organizations should implement their
    own choices of security systems on their
    networks.

Outline:

-Background
    -What is DNS-SEC?
        -DNS allows you to refer to a computer or
         network by name, like "byu.edu" instead
         of a numerical address
        -DNS makes the internet easier to use
            -Ease of use is what made the internet
             popular
            -The internet is now the backbone of
             commerce and communication
        -DNS has security holes; was designed in
         a more trusting time
            -Attacks on DNS infrastructure
            -Attacks on individual businesses
        -DNS-SEC is intended to fix those
         problems
-Introduction
    -DNS-SEC has problems of its own
        -Network delays
        -Can still be hacked
    -Governments are in the process of adopting
     DNS-SEC
    -Government should stay out of it, private
     organizations should make individual choices

-The internet has always been community based
    -"Requests For Comments" are released instead
     of enforced standards
        -Community participation leads to more
         flexible, more robust solutions
        -DNS-SEC was released as a series of
         RFC's
        -Implementation is optional - you can do
         things however you want
    -The flexibility of the internet and private
     innovations led to the internet's growth
        -The most popular products used on the
         web are run by communities and
         corporations
        -Things like VoIP, webcams, etc... exist
         and were invented because of flexibility
    -The government often makes poor decisions
     when they're isolated from professionals
        -Most professionals favor DNS-SEC
         adoption, but how the government runs it
         is in question
        -example: A state legislature tried
         passing a bill to change the value of PI

-Privacy concerns regarding government control of
 DNS
    -The same debate as privatization vs.
     nationalization
    -Government implementation of DNS-SEC could
     lead to censorship like in China and
     Australia
        -Economic and social concerns
    -Government control could lead to security
     breaches
        -"Deep-packet sniffing" uncovered in the
         UK - the government controlled
         infrastructure and abused it

-DNS-SEC isn't the right solution everywhere
    -DNS-SEC causes an increase in internet
     traffic and would slow down individual
     requests
        -Technology shouldn't get in the way of
         the people it's supposed to help, even
         if it is "secure"
    -Individual implementations allow flexibility
     and increased security
    -DNS-SEC doesn't even fix all the problems
        -All the old attacks still work, they're
         just harder
        -People will always find a way around
         some measure
        -The key is diversity

2 comments:

Lance Harper said...

Make sure to explain well all the technical terms or the reader will lose interest because it doesn't seem relevant to them. I would use the format where you present the audience's arguments first and then present yours in the last paragraphs so you can acknowledge their arguments yet prove yours and finish with a strong persuasive conclusion.

Sean said...

I definitely agree with your first point - I'm going to focus a lot of my editing time on making sure that my definitions are simple, clear and powerful. I'm also trying to include lots of practical examples so people see that even if they've never heard of these systems, they rely on them every day.

Thanks for the tip on the structure of the essay - that sounds right to me!