__________________________________________________________
/ _/__ / /____ ____/ |/ / _/ ___/ / |/ /__ _ _____
_/ // _ \/ __/ -_) __/ // // /__ / / -_) |/|/ (_-<
/___/_//_/\__/\__/_/ /_/|_/___/\___/ /_/|_/\__/|__,__/___/
----------------------------------------------------------
February 1997 - Volume 2, Issue 2 - Table of Contents
FEATURE ARTICLES:
A Domain is Born: How Ideas Become Addresses at the InterNIC
What it Means to be a Registry
Digital ID's: Establishing Internet Trust
Call It in the Air: Client-Side Scripting on the Web
REGULAR ARTICLES:
[Calendar of Events]
What's in a Name? A Graphical Look at Registration Info
End User's Corner - FTP or not FTP: That is the Question.
The 15 Minute Series UPDATE - The latest modules, feedback,
and FAQs on the 15 Minute Series
Performance Measures: Stats for the most recent month
EDITORIAL SECTIONS:
User Feedback - Tell us what you'd like to see in the
InterNIC News
Letters to the Editor
Meet the News Staff
InterNIC News Awards and Recognition
Using this material
Other ways to receive the InterNIC News
_________________________________________________________________
FROM THE EDITOR
[Editor Icon] by Hope Glass, Information & Education Services
_________________________________________________________________
>From the Editor
24 X 7 TOLL FREE NUMBER COMING TO INTERNIC IN FEBRUARY!
What does it take to be a successful registry? Listed among the
many requirements detailed in this month's cover article by Robin
Murphy is the statement, "A willingness to grow and change to
meet unpredictable demand." In February, Network Solutions,
Inc. and the InterNIC will introduce a new 24 x 7 toll-free
number to meet the growth in demand for credit card payment
services. This new service will provide an alternative method for
quickly processing customer requests. Look for details on the
InterNIC Web site later this month. This issue we are introducing
our first article in a series that explores the domain name
registration process. A Domain is Born: How Ideas become
addresses at the InterNIC offers a step-by-step explanation of
how to register a domain name with the InterNIC. Be sure to check
periodically for our latest overview article. We think you will
find these "cheat sheets" indispensable.
Pete DeVries, Net Scout's Internet Tools Specialist, attended the
MacWorld Conference and he reports in this month's End User's
Corner that Apple is still alive and kicking! Their new Operating
System, code named Rhapsody, is due out in the summer of
1997. Mac and PC Web Developers will be interested in our Web
Technology article: Call It in the Air: Client-Side Scripting on
the Web. Dan Rinzel, our Webmaster shows you how these new
scripting languages are bending HTML in new directions. We always
enjoy hearing from our readers. Write and let us know what you
would like to read about in future issues of the InterNIC News.
Warm regards,
InterNIC News
__________________________________________________________
/ _/__ / /____ ____/ |/ / _/ ___/ / |/ /__ _ _____
_/ // _ \/ __/ -_) __/ // // /__ / / -_) |/|/ (_-<
/___/_//_/\__/\__/_/ /_/|_/___/\___/ /_/|_/\__/|__,__/___/
----------------------FEATURE ARTICLE---------------------
A DOMAIN IS BORN: HOW IDEAS BECOME ADDRESSES AT THE INTERNIC
by Robin A. Murphy, Information & Education Services
_________________________________________________________________
So you've decided to jump on the bandwagon and establish an
Internet presence. You know that one of the first steps is
getting a domain name - but you don't have the first clue how to
go about it.
Or maybe you already are one of the almost one million
individuals or organizations with a domain name - but you
couldn't explain the process to save your life.
Well, you are in luck.
At the InterNIC, the global registrar for .com, .net, .org, .edu,
and .gov, we maintain a wealth of documentation, available via
both web [http://rs.internic.net/rs-internic.html] and ftp
[ftp://rs.internic.net/], to help you with registering and
maintaining your domain name. We also have developed a range of
tools to simplify, streamline, and speed the task. And if needed,
our help desk staff is available 15 hours a day to answer your
questions and assist you at any point in the process.
Nevertheless, whether you are approaching the InterNIC for the
first time, or you feel as though the registration process is
tattooed on your brain, it helps to get a feel for the "big
picture." So, to help newcomers and old hands alike, we are
offering a step-by-step overview of the registration process.
We have also developed a flowchart to graphically depict domain
name registration, available at
http://rs.internic.net/domain-info/domflow.html. Click on the
miniature flowchart at right to get an "at-a-glance" overview.
We hope this review helps you make a name for yourself on the
'Net!
How a domain becomes a domain:
Step One - Preparation
Proper preparation will save you headaches later and help prevent
delays in the process.
Due to the fact that the domain naming system requires unique
addresses, no two domain names can be the same. So the first
thing to do is to find out if the domain name you want is
available. This is easy - simply search the InterNIC's Whois
database to see if there is a match for the name you want. The
Whois database contains records for all of the domains that have
been registered with the InterNIC, as well as information on over
200,000 networks. You will find an easy-to-use web interface to
the Whois database at http://rs.internic.net/cgi- bin/whois. If
there is a match, the name that you want is already taken and you
will have to come up with an alternative choice. If there is no
match, then the name is available and you can register the domain
name for yourself.
The next thing you will need to do is contact your Internet
Service Provider (ISP) and arrange for domain name service. What
is domain name service? Well, the actual address of a computer on
the Internet is a string of numbers - the IP (Internet Protocol)
address - which can be hard to remember. Domain names offer us an
alternative - an alphabetical, hierarchical, and much more
logical system of Internet addresses. The problem, however, is
that the network depends on the numerical address. So, in order
to use domain names, we rely on machines called name servers,
which "translate" domain names into their corresponding IP
address. This process is called "resolution." Your ISP most
likely maintains one or more name servers, and can provide you
with this "names-to-numbers" translation - this is domain name
service. In fact, many ISPs offer general assistance with domain
name registration and some may even handle the entire
registration process for you. You should consult with your
provider to determine your options.
Without domain name service, the InterNIC will not process your
registration request, you will not be able to use your domain
name, and other people will not be able to use your domain name
to find you on the Internet.
The last thing to do before you start the registration process is
review the InterNIC's registration policies and billing
procedures. These are important documents that will affect you
throughout the life of your domain name. The InterNIC's policies
address registrants' responsibilities concerning trademarks and
can help to minimize legal disputes concerning your domain name
in the future. A careful review of the billing procedures will
help avoid problems with your domain name resulting from
confusion over payment terms. You can take a look at our policy
statements and payment procedures by visiting
http://rs.internic. net/help/index.html
Step Two - Fill out the registration template
To register a domain name, you will need to fill out the domain
name registration template. This form is used to gather the
information needed to process your registration and add your
domain to the Whois database. It is very important that you
provide complete and accurate information when filling out the
form. The information you provide is the information that is
released into the domain name system. Also, inaccurate
information can cause you problems later - for example, an
incorrect or incomplete address can prevent you from receiving
the bill for your domain name - and could result in your domain
being deactivated or deleted.
The template will ask you to supply information about yourself
and/or your organization, as well as the names and addresses of
three individuals who can be contacted concerning administrative,
technical, and billing issues for the domain. The person you
list as your administrative, technical or billing contact should
be the person best able to answer questions about that aspect of
the domain. For example, the technical contact should be able to
answer questions about the name servers you are planning to use
for your domain. You may, of course, list the same person for
more than one contact role if that is appropriate (e.g. the same
person as both administrative and billing contact). Your billing
contact will be the person to whom we send the invoice for your
domain name registration fees. You will have the option of
indicating whether you would prefer to have the invoice delivered
via electronic mail or postal mail to the billing contact.
A note of caution: select your contacts carefully, as they are
your agents and will represent you on matters related to your
domain name.
The template also asks you to list the IP addresses and domain
names of the two name servers that you will be using to translate
your domain name to your IP address.
The InterNIC provides the template in several different
formats. A plain text version of the template is available via
the web or ftp. Those without web access, or with a preference
for single page forms, can retrieve the text version, fill out
the template, and send it to the InterNIC via electronic
mail. For people who like foolproof forms, we have developed a
web interface to the template that takes you through the template
section-by-section. This web interface checks each section as you
fill it out for errors or incomplete information, and notifies
you of any problems before allowing you to proceed to the next
section. Both the text and web versions of the template can be
found in our template guide at http://rs.internic.
net/help/templates.html.
The registration template, once it is processed by the InterNIC,
becomes your agreement (contract) with the InterNIC. We recommend
that you read the document carefully.
Now you are ready to put the wheels in motion and move on to...
Step Three - Send the template to the InterNIC
To start your request moving on the road to becoming a domain
name, you need to send the template to the InterNIC. If you used
the text version of the form, simply e-mail the completed
template to hostmaster@internic.net.
If you used the web interface, the information you entered will
be used to complete the registration template. We will email you
a copy of the completed template for verification. The web
interface prompts you to tell us where to send the completed
template; the e-mail address that you enter is where we will send
the copy of the completed template - this may or may not be an
address listed in the template. You will need to e-mail this
template back to the InterNIC once you verify that all the
information is correct. Again, the address is
hostmaster@internic.net.
Step Four - InterNIC sends you a tracking number
Once the InterNIC receives your registration request, we assign
it a "tracking number" and send you an acknowledgement. The
acknowledgement is sent via e-mail to the address from which the
template was received. The subject line of the e-mail will
contain the tracking number assigned to your registration
request. The tracking number has the following format:
NIC-YYMMDD.#, where
* YYMMDD represent the year, month, and date that the
acknowledgement is sent, and
* # is the unique number assigned to your particular request.
You should immediately make a note of the tracking number - you
will need it later!
You can use this tracking number to check on the status of your
registration request (and the status of your payments - more on
that later). We have provided a simple, easy-to-use web interface
to our tracking system that allows you to type in the tracking
number and get an update on the progress of your request. You can
check out the tracking system at:
http://rs.internic.net/cgi-bin/finger.
Also, you will need to include your tracking number on any
correspondence you send the InterNIC, and you should have it
ready if you call the InterNIC's help desk.
Step Five - Your request enters the automated processing system
The InterNIC processes as many as 85,000 requests for new domain
names each month. To keep up with this demand and speed the
process, we developed auto-registration tools that enable us to
handle over 90% of these requests automatically, speedily, and
securely.
What happens to your template once the hostmaster receives your
request?
Your template is run through our auto-parser, which checks the
template for errors. Because of the volume of requests we
process, we have been able to identify the most common errors
people make when filling out the template. We have compiled a
list of these errors and assigned each a code [ftp://rs.internic.
net/domain-parser-errors.txt]. If the auto-parser detects an
error in your template, it will immediately check the list of
common error codes to see if the error matches one of the
codes. If there is a match, then the template is returned to you
via e-mail, along with an explanation of the error that caused
the problem. After you have made the necessary corrections, you
will then need to resubmit your template to
hostmaster@internic.net. Your original tracking number will
continue to apply to your request.
Remember the web interface to the template? We have taken these
errors into account in its foolproof design, in an effort to help
you quickly register your domain with a minimum amount of hassle.
If an error is detected that does not match one of the common
error codes, however, the template is placed in a queue to be
reviewed by our processing staff. The staff will attempt to
identify the problem. If the problem is immediately apparent and
easily resolved, the InterNIC's processing staff will make the
necessary corrections and process your request. If our staff are
unable to resolve the problem, they will contact you and work
with you to correct the problems and process your request.
If you submitted a complete and correctly formatted template,
your registration request will be processed immediately and you
will be notified via e-mail when processing is complete. This
generally takes less than 24 hours - with some requests turned
around in as little as 10 minutes.
Step Six - Your domain name enters Whois and the "zone"
When your template has been successfully processed, the
information you supplied will be used to create a record for your
domain in InterNIC's Whois database. Also, information about your
domain is placed in the "zone" files.
What are zone files? Zone files actually represent a distributed
database of information about domains. Each name server holds a
portion of the database. A name server keeps information, or data
files, about the domains that it resolves, and is able to "ask"
other name servers about the domains they resolve. This exchange
of information among name servers is what enables your domain
name to be resolved to your IP address from anywhere on the
Internet. A name server is considered to have "authority" over
the portion of the database - or zone - that it maintains.
The InterNIC has authority for the top level zones that contain
information for the .com, .org, .net, .edu, and .gov domains. If
you registered your domain name in the .com domain, for example,
the InterNIC will release the information about your domain name
into the COM zone files, which have authority for the .com
domain. We release information into the zone files once a day,
every day, five days a week.
As you can see, once the information for your domain name has
been added to the Whois database and released into the zone
files, a portion of the information provided on your template
becomes accessible to anyone on the Internet.
Step Seven - InterNIC sends you an invoice
Registering your domain in .com, .org, .net, .edu, or .gov costs
$100 (US). This fee covers the cost of your initial registration
and updates to your domain name's record for a period of two
years.
Updates will cover most of the changes you may need to make to
your domain name record. For example, you can change your phone
number, or the name of your billing contact if someone in your
accounting department quit and someone else took over. There are
some changes, however, that are not covered and actually require
a new registration request. These include changing the name of
the organization that registered the domain name, transferring
the domain name to another party, and changes to the domain name
itself.
We will automatically send you an invoice for your domain name
within seven days. It is up to you how you will receive your
invoice; the template asks you to check either e-mail or postal
mail.
The invoice will include:
* your name and address
* the date payment is due
* the amount due
* the period covered by the payment
* an invoice number
* your domain name
* the tracking number that was assigned to your registration
request
* brief information about paying by check, credit card, or
account
* a tear off stub to send in with your payment (if you are
paying by check)
* the address to send your check payment to (note there are two
separate remittance addresses, one for e-mail invoices and one
for postal invoices; the remittance address appearing on your
invoice will depend on which one of these delivery methods you
checked in your template)
* a phone number and e-mail address you can use to contact our
billing department if you have questions
You should review this information carefully to make sure it is
correct.
_________________________________________________________________
Why charge a fee?
The hardware, software, engineering talent, staff, infra-
structure, and other resources needed to run a domain name
registry cost money. Prior to the introduction of fees in
September of 1995, the costs associated with managing the domain
name registration process were paid by the Federal Government
(i.e. subsidized by US taxpayers).
The explosive growth of the Internet over the past several years
quickly threatened to exceed the government's ability to
underwrite domain name registration. The increasingly commercial
nature of the Internet also raised questions concerning how
appropriate it was to continue government funding of domain name
registrations. The National Science Foundation recognized the
potential of the Internet to become a mass medium and the need to
transition domain name registration from a taxpayer supported
activity to one supported by the industry and those using the
service. This transfer of costs was always one of the open-ended
goals of the National Science Foundation's cooperative agreement
with Network Solutions, the company that runs the InterNIC's
domain name registration activity.
Mid-way through the five year cooperative agreement, an
independent panel convened to review the performance of the
awardees and recommended the introduction of fees for domain name
registrations. These fees were implemented to provide the funds
needed to operate and continue to expand the registry in the face
of a demand that drove project costs beyond the funding provided
by the National Science Foundation.
_________________________________________________________________
Step Eight - You pay for your domain registration
We offer a range of payment options: check, credit card, First
Virtual's VirtualPIN(tm) method, and - for Internet Service
Providers - debit accounts.
You can pay for your domain with a check by simply making out the
check to InterNIC Registration Services and sending it, along
with the stub from your invoice, to the address listed on the
invoice.
There are a variety of ways to use your credit card to pay for
your domain. We are implementing an interactive voice response
system for our credit card customers. You will be able to simply
call the 1-888 number anytime - 24 hours a day, seven days a week
- and provide your credit card information to the system to pay
for your domain registration fees. First Virtual logo If you are
all for electronic commerce but a little nervous about sending
your credit card number into cyberspace, you can opt for First
Virtual's VirtualPIN(tm), which allows you to use the web to
authorize charges to your credit card, but keeps your sensitive
credit card information offline - between you, your bank, and
First Virtual. Applications for the VirtualPIN(tm) can be found
at our website - check out
http://rs.internic.net/cgi-bin/fv/payment.
Remember that tracking number? You will need it to use the
VirtualPIN payment method.
If you frequently register large numbers of domains with us, you
may also set up an account with the InterNIC.
More detailed information about invoicing procedures and payment
options can be found at http://rs.internic. net/help/index.html
What happens if you don't pay?
Under normal conditions, if we have not received your payment by
12:00 PM (Eastern Standard Time) on the due date, we will send
your administrative, technical, and billing contacts a 15 day
"deactivation" notice via electronic mail. In addition, a 15 day
deactivation notice will be physically generated and mailed via
the U.S. Postal Service to the person you listed as the
"registrant" (section three of the template) in your registration
template.
You have 15 days from the date of this notice to send your
payment to the InterNIC. If we do not receive your payment by the
deactivation date, we will deactivate your domain name - remove
it from the DNS service.
Under normal conditions, if your domain name is deactivated you
may still have 60 days to send us your payment. We will apply
your payment and your domain will be "reactivated." However, if
we still have not received your payment by the 61st day following
the deactivation date, your domain will be returned to the pool
of available domain names, and you will be notified that your
domain name has been released and is available for any other
party to register.
Use our web-based tracking system (and your tracking number!) to
check on the status of your account. Again, the URL for the web
interface is http://rs.internic.net/cgi- bin/finger. If you are
experiencing payment problems, we have implemented a web-based
form you can use to report problems with your account, found at
http://rs.internic.net/forms/mail_billing1.html.
Step Nine - You renew your domain with the InterNIC
Following this initial two-year period, you will be charged $50
(US) annually, on the anniversary of your initial registration,
to renew your domain name. This fee covers the cost of processing
your renewal and also includes updates to your domain name record
for that year.
Your billing contact will receive an invoice for your domain name
renewal, 30 days before it is due. Just as with new
registrations, if we have not received your payment by 12:00 PM
(Eastern Standard Time) on the due date, we will send your
administrative, technical, and billing contacts a 15 day
"deactivation" notice via electronic mail, and a 15 day
deactivation notice will be physically generated and mailed via
the U.S. Postal service to the person you listed as the
"registrant" (section three of the template) in your registration
template. If you do not pay within 15 days of the date of the
deactivation notice, your domain will be deactivated. If you
still have not paid sixty days after deactivation, your name will
be deleted, removed from the domain name system and the zone
files, and returned to the pool of available names for someone
else to register. [Number 10 icon]
Step Ten - Enjoy your new address on the information superhighway!
Domain names represent places to go - answers to questions -
things to buy - ways to make money. You can teach a course, sell
galoshes, or start a grassroots community organization. With a
domain name you can make yourself, and all that you may have to
offer, known on the Internet.
At the InterNIC, we are standing by, ready to help you turn your
ideas into an address.
_________________________________________________________________
__________________________________________________________
/ _/__ / /____ ____/ |/ / _/ ___/ / |/ /__ _ _____
_/ // _ \/ __/ -_) __/ // // /__ / / -_) |/|/ (_-<
/___/_//_/\__/\__/_/ /_/|_/___/\___/ /_/|_/\__/|__,__/___/
----------------------FEATURE ARTICLE---------------------
WHAT IT MEANS TO BE A REGISTRY
by Robin A. Murphy, Rich Landers, David Graves, and Tom Newell,
Information & Education Services
_________________________________________________________________
What does it mean to be an Internet registry? On the surface,
this question seems easy to answer. An Internet registry is
responsible for keeping track of domain names, an addressing
construct that enables computer-to-computer communication across
the networks that comprise the Internet.
Without the services of a central naming registry, the Internet
would cease to function. While people can employ a wide variety
of symbols and mnemonics to remember and convey addresses,
Internet connected computers must rely upon more deterministic
methods like numeric assignments. For example, if an Internet
user wishes to retrieve information from a World Wide Web site at
the domain name of "www.example.com", because computers use
numeric-based addressing mechanisms (Internet Protocol numbers),
an intermediary translation device is required to make that
transaction possible.
Domain names partner with directory "resolution" techniques to
form the Domain Name System (DNS). The DNS is designed to help
both users and their applications locate other machines on the
Internet, mapping between human-friendly names and their
associated numeric IP addresses. However, because addresses on
the Internet must be unique - no two machines can use the same IP
number and no two domain names may be the same - a central
registry is needed to manage the assignment of domain names to
provide information about these assignments to the core, or
"root" of the Domain Name System.
Network Solutions, Inc., the company which operates the
InterNIC's Registration Services under a cooperative agreement
with the National Science Foundation (NSF), serves as the
exclusive registry for the .com, .org, .net, .edu, and .gov
top-level domains. As a full-service registry, Network Solutions
also maintains a strong commitment to support the needs of a
growing constituency that includes end-users, Internet trainers,
Internet service and content providers, K-12 organizations, and
higher educational institutions.
Since 1993, when Network Solutions began providing registration
services to the global Internet community, the Internet has
evolved, moving from a network that focused on communication
among researchers and educators to an exploding marketplace of
products, services, information, and entertainment. Network
Solutions has had a front row seat for this transformation. As a
result, the company is in a unique position to provide an answer
to the question: "What does it really mean to be a registry?"
A willingness to grow and change to meet unpredictable demand
When Network Solutions took on the registry functions, the system
in use for keeping track of domain name assignments consisted of
a "flat" text file which was compiled manually and distributed
via file transfer protocol (ftp). It was observed that this was
not a system well-suited to the scalability of the growing
Internet. Network Solutions was faced with devising a way to
perform the registry functions that would not only meet the
demand, but allow the network to grow at a pace ruled by popular
demand rather than technical constraint.
Meeting the burgeoning demand for registration services required
people, space, talent, and speed. These requirements have
real-world financial and organizational implications. Network
Solutions has tripled the size of the staff to handle the needs
of an exponentially growing customer base. Considerable effort,
time, and money have been devoted to recruiting and retaining the
engineering talent needed to facilitate innovation and automation
- so essential to the development and maintenance of a scalable
and rapid registration process. It is a fact of life that when
you add more people and more equipment, you need more physical
space and more infrastructure. The logistical challenges of
continually growing the registry have been staggering - but they
have been met. In 1992, the total domain name space did not
exceed 4,000 registered names, grew by fewer that 300 names per
month, and accounted for an average of four weeks to process a
single registration request. Today, those figures are 900,000 and
85,000 respectively, and registrations are safely and securely
completed for over 90% of new registrants in less than 24 hours.
A willingness to face problems and find solutions
Because the function of a registry is critical to the function of
the Internet, problems cannot go unsolved and challenges must be
met. Network Solutions is keenly aware of the need to face
problems and find rapid, scalable solutions before difficulties
even surface.
Innovation, hard work, forward-thinking, and research and
development are necessary to move the registration process beyond
the technological thresholds of the past. A first-hand
understanding of the Internet's user community, particularly the
varied and often competing interests of this community, is
indispensable to fulfilling the registry's mission, as is an
awareness of the impact of the Internet's evolving role on our
society, our institutions, and our daily lives. Thorough
knowledge of existing commercial and legal mechanisms is needed
to respond to the inevitable clashes that occur as this new
medium collides with a social and legal infrastructure that
predates borderless, global communication networks.
Against what at times appeared to be insurmountable odds, Network
Solutions marshalled the effort needed to overcome challenges
presented by volume, speed, reliability, security, law, supply
vs. demand, and impartiality. The results of the registry's
initiative are evidenced by:
* a robust, redundant, and secure development, engineering and
support environment for registry operations representing an
investment of $4 million in the last year alone towards
networking and computing technology.
* reduction in the turn-around time for new registration
requests - from more than four weeks to less than 24 hours -
in the face of exponential growth.
* the development of user registration aids and tools that open
the process up to a wider, less technically inclined group.
* the ability to protect a domain name record and authenticate
requests for changes to the record in the form of Guardian, an
authentication system which offers multiple levels of security
for contacts associated with domain name records.
* a policy framework that balances the divergent interests of a
broad community, has been successful at minimizing legal
conflict, and has helped domain name disputes stay between the
conflicting claimants.
A willingness to take risks
Pioneers in any arena accept risk as part of the bargain; it is
impossible to make progress without it. Technology development,
business ventures, and legal pursuits all pose certain risks to
the parties involved. More often than not, the risk is shared and
the outcome of the efforts affect those both directly and
indirectly involved. As the first and only international registry
of its kind, Network Solutions was charged with engineering the
transition of domain name registration from a publicly-supported
activity to a fee-for-use system. Although the risks involved in
spearheading this unprecedented effort clearly have the potential
to affect a broad community, no entity has been or remains more
directly affected than the registry itself and the company that
operates it.
The financial risks for Network Solutions have been substantial.
Funding the existing level of registration activity was not an
option; Network Solutions had to fund a registry that was capable
of handling unpredictable and explosive growth in the demand for
its services. Although the registry was initially funded by the
NSF under the cooperative agreement, the demand for domain names
soon outstripped the government's ability to support the
registry's operation. The implementation of registration fees was
recommended and approved by the NSF as the next logical step in
effecting the transition to a user-supported registry.
Network Solutions had to find a way to fund the registry at a
level that would support future demand, make financial forecasts
about an unprecedented phenomenon, invest the financial resources
necessary up front in order to honor its contractual obligations
and community responsibility, and implement a fee-for-use system
with minimal cost to the user. Balancing the open tradition of
the Internet with increasing commercial interest is no small
task. Combine this balancing act with developing a commercially
viable registry capable of handling unlimited potential demand,
and you have Network Solutions.
The Internet's emergence as a commercial medium poses unique
dilemmas for our society's legal system. Trademark holders and
domain name holders often find themselves on opposite sides of
the question: Who has the right to use a domain name? Network
Solutions, as the registrar for the .com domain, has had to
address the legal risks associated with being the registrar -
without governmental immunity in situations where no legislative
or case law existed to serve as a guide. In an effort to balance
the rights of nearly 12 million trademark owners with hundreds of
thousands of domain name registrants, Network Solutions crafted a
Domain Name Dispute Policy to protect the registry from
litigation which could have negatively and severely impacted its
ability to manage the domain name space. This policy has been
effective at keeping disputes concerning trademarks and domain
names where they belong - under the purview of the courts.
Network Solutions' policy has been so effective, in fact, that
other registries for top level country domains have either
adopted the policy or used it as a model for their own policies.
Agents of change occupy difficult positions, putting their
resources and reputations on the line to achieve new levels of
knowledge and possibility for those who will follow. Network
Solutions has willingly assumed the risks associated with being
an agent of change in light of the opportunity to play an
important and necessary role in the development and evolution of
the Internet.
A willingness to operate under pressure
Under the terms of the cooperative agreement between Network
Solutions and the NSF, the InterNIC's Registration Services were
required to become fully operational on day one of the agreement
and to remain fully operational at all times. These requirements
removed any possibility of a comfort zone. Network Solutions had
to define problems, investigate and come up with solutions, and
implement the solutions with no "time-off" for learning or
experimentation. There was no margin for trial and error.
The growth of the registry took place in full view of the public
- like a play without a rehearsal or a publication without a
draft.
The data that represented the registration record prior to 1993,
when Network Solutions took on the registry task, was inherited
as a flat file. While a flat-file construction had served the
registration requirements of the past, it was inadequate to meet
the level of demand facing Network Solutions when they assumed
responsibility for registration services. The need to migrate
from a flat-file construction to a relational database
environment that would scale with demand was clear. This
migration took place in a fully operational setting. Network
Solutions was not in a position to post signs that said "Closed
for renovations - please pardon our dust while we build a better
registry."
The implementation of a fee for domain name registrations and
renewals, a seemingly simple task, necessitated a "back-office"
requirement of monumental magnitude. Network Solutions had to
implement an invoicing, collections, and reconciliation system
that could accommodate both paper and electronic invoices and
handle hundreds of thousands of payments by check, credit cards,
and electronic methods into a fully operating project overnight -
with essentially no phase in period.
Relentless increases in workload required equal increases in
resources. The organizational structure of the company also felt
the pressure of the growth, and Network Solutions continually had
to define and reshape itself in ways that accommodated the
mission of the registration effort and the needs of the
registration services customer. Growth in the size of the staff
and the size of the domain name database generated requirements
to rapidly expand the operations center network and to provide
computer processing power that constantly pushed the envelope of
the capabilities of existing hardware and software. Further, this
demand pushed the existing staff, particularly software engineers
and system administrators, to their limits in integrating the
elements and fine-tuning the system to optimize performance.
Despite this enormous pressure, Network Solutions has succeeded
in repeatedly finding a path from problem to solution, as
evidenced by the current success rate of registrations, the
reduced turn-around time for processing, easier payment methods,
and security options that have been introduced. Most remarkably,
for no extended period during the maturation of the registry has
the system for domain name registrations in .com, .org, .net,
.edu, and .gov been unavailable to the Internet community.
A willingness to play an active role in the evolution of the Internet
The Internet is a work in progress. Technological development
continues, but equally importantly so do discussions concerning
issues such as Internet governance, Internet address management,
and equitable distribution of the costs associated with operating
a registry, among other topics. As the registrar for .com, .org,
.net, .edu, and .gov, Network Solutions has continually found
itself somewhere between the center of activity and the head of
the pack in these discussions.
It is impossible to serve as a global registry and not be
involved in the evolution of the Internet and the attendant
issues. What makes a difference is whether this involvement is
embraced or ignored. Network Solutions has responded by playing
an active role in the Internet community. The Internet
Engineering Task Force (IETF), along with the Internet
Engineering Steering Group (IESG) provide a framework for
gathering feedback and reaching consensus on technical issues
facing the Internet community. Network Solutions actively
participates in the three IETF meetings each year. At these
meetings, representatives of the registry have engaged in lively
and open discussion of issues that have an impact on registration
activities. This exchange of information has provided Network
Solutions with invaluable input, without which the activities of
the registry would not represent the consensus of the Internet
community.
The numeric addresses used by machines on the network - IP
numbers - are a finite resource in great demand. Working with the
Internet community, Network Solutions drafted guidelines to
encourage the responsible and effective use of IP numbers under
IPv4. These efforts brought Network Solutions together with other
Internet organizations, such as The Internet Assigned Numbers
Authority (IANA), the National Science Foundation (NSF), the
Federal Networking Council (FNC), the IETF, and IP registries
such as Reseaux IP Europeens (RIPE) and the Asia Pacific Network
Information Center (APNIC), to explore the best possible methods
for overseeing IP number allocation for tomorrow's Internet
community.
In other fora, Network Solutions is equally active, seeking to
lend the benefit of its experience to debate on issues such as
new top level domains and Internet governance.
Playing such a pivotal role is not without its drawbacks,
however. Taking a stand or making decisions that have the
potential to affect millions of users is bound to attract
critics. Participation in the evolution of the Internet means
considering the needs of today's users against those of
tomorrow's users, the interests of the individual or group
against those of the broader community. It is impossible to
please everyone. Introducing the "fee-for-service" concept to the
Internet, a medium that traditionally has been thought of as
rightfully free (as government subsidized services often are),
was a necessary but contentious undertaking. Network Solutions
has assumed a leadership position in all areas affecting or
affected by the registry, never retreating from its potential to
offer a significant contribution to the evolution of the
Internet.
A willingness to meet the needs of all customers
Network Solutions is required, under the terms of the cooperative
agreement, to provide domain name registrations. Running a
registry, however, must reach beyond the technical and
engineering obligations to include tools, resources, and
educational programs that support the registration activity and
the user community.
As the Internet reaches more and more people, the audience that
the registry must support comes from an increasingly wider range
of technical backgrounds. Internet Service Providers (ISPs)
serving thousands of customers use our services on their
customers' behalf. Soccer moms band together to register a
domain name and establish a website for their community soccer
league. Network administrators for Fortune 500 companies require
security for their domain names and associated records.
Recognizing that supporting customers is in the best interests of
the registry, the Internet, and the company, Network Solutions
has aggressively pursued the development of a robust help desk,
user-friendly registration tools, documentation, and wide-ranging
distribution avenues for these services. Being a global resource
means that customers come from every time zone and speak a
multitude of languages - hence a help desk with extended hours
and multilingual staff is needed to meet the needs of some
customers. Simple, non-technical language and step-by-step
guidance is essential to serving those from non-technical
backgrounds. The fact that Internet access does not always mean
graphical capability and World Wide Web access means that
services must function at a level that accommodates other, more
basic types of Internet access - e-mail and ftp.
Automating processes delivers faster service. Implementing an
increasingly wider array of payment options provides customers
with more choices. Offering elective levels of security provides
safety for customers' transactions.
In addition, however, Network Solutions is committed to
supporting the research and educational community, to whom the
Internet owes much of its beginnings. Institutions and
organizations in this community will find a range of educational
materials and current awareness services designed to assist them
with supporting their own Internet end users. Training
materials, presentations, tutorials, newsletters, and mailing
lists are offered free of charge to help researchers and
educators, as well as the broader Internet community, make the
most of the medium that represents such an intrinsic part of
Network Solutions' activities.
What does it mean to be a registry?
Being an Internet registry means accepting constant change,
embracing challenges, looking at problems as solutions waiting to
happen, taking considerable risks because the risks are worth the
benefits to the broader community, withstanding constant and
unrelenting pressure of all sorts from all directions, listening
to critics, stepping up to the plate and honoring the position
with active, thoughtful, and considered participation in Internet
development, and meeting the needs of potentially anyone from
anywhere who needs help with registry services.
Network Solutions has been repeatedly recognized for meeting and
exceeding expectations for registration and network information
center services. In November of 1994, an independent panel of
industry experts convened by the National Science Foundation
applauded Network Solutions' success in retaining an end user
focus while accommodating and nurturing growth. In August of
1996, Network Solutions was awarded the John Dvorak Award for
Outstanding Commercial Internet Company of the Year in
recognition of its contributions to the Internet community. And
most recently, the registry was nominated for one of the
Computerworld Smithsonian Awards, which honors innovators whose
vision in using information technology produce positive social,
economic, and educational change.
Over the course of operating the registry, Network Solutions has
faced unprecedented and unparalleled challenges. Their efforts
have met these challenges and have helped to make the syntax of
domain names - example.com - common household language. Every
person on the planet who works, shops, learns or plays in .com,
.org, .net, .edu, and .gov benefits from the work performed by
the registry each day. Perhaps a better question would be "What
does it take to be a successful registry?" Network Solutions is
working on the answer.
_________________________________________________________________
__________________________________________________________
/ _/__ / /____ ____/ |/ / _/ ___/ / |/ /__ _ _____
_/ // _ \/ __/ -_) __/ // // /__ / / -_) |/|/ (_-<
/___/_//_/\__/\__/_/ /_/|_/___/\___/ /_/|_/\__/|__,__/___/
----------------------FEATURE ARTICLE---------------------
DIGITAL IDS: ESTABLISHING INTERNET TRUST
by Tom Newell, Manager, Information & Education Services
_________________________________________________________________
Consider the process of authentication. Authentication is at the
heart of commercial exchanges. Pay for groceries by check at the
corner market? Show a driver's license. Withdraw money from your
bank account? ID please. Even ATM transactions trace the initial
establishment of a trusted relationship to proof of
identity. Based upon physical recognition, we feel comfortable
granting trust to others - in some cases, to such a degree we
give them our money!
In this digital age, the problem of authentication is made more
complex as a result of distributed information exchange,
automated processing routines, and the capability to establish
and build relationships without physical proximity. Much like
crossing the boundaries of our geographic space requires visual
proof of identity (passports), traversing the growing virtual
expanse of "cyberspace" can sometimes require a similar means of
identification and trust building.
On the Internet today, it is possible to make credit card
purchases, access banking services, use subscription-based
content services, and exchange sensitive or private
information. But to do it safely and securely requires trust. How
do we establish that trust? One method is through the use of
Digital IDs. Digital IDs make it possible to prove your identity
in electronic transactions, much like a driver's license or a
passport does in face-to-face exchanges. With a Digital ID, you
can assure friends, business associates, and online services that
the electronic information you provide originates from you. On
the Internet, you can present a Digital ID electronically to
identify yourself or to gain access to online information
services.
Digital IDs are also known as digital certificates and they make
use of "Public Key Cryptography" to associate electronic keys
with an "identity," allowing encryption and digital "signing" of
electronic messages and exchanges. Using public key encryption
techniques, Digital IDs use a public key and a private key. The
public key is made available to anyone who wants to interact with
the owner of the ID and is used to verify a message signed with
the private key. It can also be used to encrypt messages that can
in turn only be decrypted using the private key. The security of
such messages encrypted in this fashion thus depends upon the
protection of the private key in much the same fashion as we
protect ATM Personal Identification Numbers (PINs) or our house
keys.
Digital IDs are issued by a Certification Authority (CA), such as
Verisign, and are digitally "signed" by that CA as a "stamp of
authenticity." The ID consists of a few common elements including
the owners public key, their name, the expiration date of the
public key, the name of the CA, a serial number, and the digital
signature of the issuer (CA). In their most generally accepted
form, Digital IDs are described by the X.509 international
standard (see http://www.itu.int/) in order to ensure their
interoperability with applications written to conform with the
standard.
So how do you make use of a Digital ID? Typically used in
electronic commerce, Digital IDs allow consumers to establish a
"trust" relationship with vendors, determining their identity
using the vendors ID issued by a CA. In fact, most of the popular
WWW server software supports the Digital ID concept for secure
exchanges, facilitating the trust building process. Before
issuing the ID to the vendor, a CA such as Verisign has
established that the vendor is who they claim by examining
business records and other identifying materials. Because a
secure exchange is not enough to establish the trust necessary
before a consumer provides credit information, Digital IDs
provide a more complete solution in assuring the identity of all
parties involved in a transaction.
There are several types of IDs though they fall into one of two
categories - IDs that identify individuals and IDs that identify
organizations. Digital IDs are available for individuals to
install in their WWW browsers or their S/MIME
(Secure/Multipurpose Internet Mail Extensions) applications to
gain access to remote services which require a higher degree of
authentication. Digital IDs are also available for Internet-based
merchants for use within their WWW servers to identify themselves
to their customers. Digital IDs are additionally available for
vendors who distribute software using the Internet to provide
assurance to customers downloading their product. Each ID is
available at various "classes" with each class providing a higher
degree of assurance and thus requiring more information be
provided the CA before the ID is issued.
Want to learn more? I recommend the following:
An introduction to Digital IDs
http://digitalid. verisign.com/id_intro.htm
Digital ID Frequently Asked Questions (FAQ)
http://digitalid. verisign.com/id_faqs.htm
Pretty Good Privacy (PGP)
http://world.std. com/~franl/pgp/
A comprehensive collection of PGP information
1997 RSA Data Security Conference (January 28-31, 1997)
http://www.rsa.com/conf97/
S/MIME: Anatomy of a Secure E-mail Standard
http://www.ema.org/html/pubs/mmv2n4/s-mime.htm
_________________________________________________________________
__________________________________________________________
/ _/__ / /____ ____/ |/ / _/ ___/ / |/ /__ _ _____
_/ // _ \/ __/ -_) __/ // // /__ / / -_) |/|/ (_-<
/___/_//_/\__/\__/_/ /_/|_/___/\___/ /_/|_/\__/|__,__/___/
----------------------FEATURE ARTICLE---------------------
CALL IT IN THE AIR:
CLIENT-SIDE SCRIPTING ON THE WEB
by Dan Rinzel, Webmaster, Information & Education Services
_________________________________________________________________
What is all this Scripting Stuff?
Anyone keeping an ear out for the latest developments in the
development of Web sites has doubtless stumbled across a
bewildering list of "new languages" in which Web sites can be
designed. JavaScript(tm), LiveWire, JScript, VBScript,
ActiveX(tm), and Java(tm) lead an often confusing parade of these
somewhat mis-named "scripting languages," which can in turn leave
even seasoned Web developers pondering whether the need for
HyperText Markup Language (HTML) is passing away.
The short answer to this is "not any time soon." Even the most
robust of these tools requires some "hook" into the Web world,
and that hook is invariably through at least one html tag in a
Webpage. And yet, even the weakest of these languages can take
Webpages in directions that the tags of html were never designed
to go. The ability to create custom surfing experiences is the
glittering coin offered by client-side scripting tools, and Web
site developers would be well served to watch the coin closely
while it is airborne.
Request-Response
A brief overview of the transaction structure of the Web, known
as HyperText Transfer Protocol (HTTP), should suffice to show why
these tools should supplement the toolbox of any Web Developer,
alongside
tags and tags.
_________________________________________________________________
For an introductory analysis of HTTP see the InterNIC 's 15
Minute Series module on HTTP, available at:
http://rs.internic.net/cgi-bin/15min/mkmodule.cgi/http/sld01.html
For a detailed technical specification, see
http://www.graphcomp.com/info/specs/http10.html
_________________________________________________________________
Succinctly, a Web transaction consists of a request by a browser
computer (a client) to a host computer (a server) where a Web
site resides. The server responds to the client with the page
requested, or an error message of some kind. That request may
spawn several other requests, for image files to load onto a
page, or for some reaction to the user clicking the 'Submit'
button on a form, but the "request-response" structure is the
basic unit of HTTP. HTML, in turn, developed as a series of codes
to tell the client what to do with the page returned: special
layout instructions that could include links, or opportunities to
make further HTTP requests. In this model, the client is
primarily a "slave" to the server - receiving input from the
server, but not using any of its own computer power for anything
other than layout decisions.
As the expanding explosion of Web traffic hit, it
became clear that serious limitations to this transaction
structure exist. It may be fine to request a simple text page
from a server one or two hops away, but to engage in multiple
repetitions of request-response (such as those required by many
forms that must be validated) with a server halfway around the
world that is also responding to requests from tens of thousands
of other clients is tedious at best, bad business at worst, and,
thanks to these new "client-side scripting languages,"
increasingly unnecessary.
What developers of browser software discovered was that, by
"exposing" many client events (mouse clicks, text typed in a text
box) to a script compiler that is a piece of the browser, web
servers could send instructions coded directly into Webpages,
that could be run ONLY IF certain conditions were met by the
individual user, and could dynamically reflect user input, using
the computing power of the client without reference to the
server.
For an example of the difference, see the Web version of this
article at http://rs.internic.net/nic-support/nicnews/feb97/
scripts.html
* Client-side Scripting Form: No additional requests made.
All the interpretation is done right on your machine.
* Server-side Scripting Form: Two additional requests,
plus time for the server to interpret the input before returning.
Note that the client-side script was able not only to "capture"
what you typed, but make a decision about it and return HTML that
contained a "dynamic" tag for background color - the same
behavior that the server-side script did. In addition, the
client-side script was able to take advantage of the browser
software's ability to manage client-side objects and create a new
window (which will close itself after 3 seconds) or alert box.
>From this frivolous example, you can see the performance
advantages to using the client's processing power to alleviate
bottlenecks on the server, and you can see some of the functions
it is possible to build using one of the client-side scripting
languages...
What about Java? Everything's Java Now, Right?
Despite its mass media popularity, Java, along with the other
Object-Oriented Programming Languages (OOPLs) like Visual
Basic(r) and C++, doesn't really fit into this niche. Both Java
"applets" and ActiveX "controls" can be embedded into html pages,
using tags like