# Routing must be accomplished on either a 9-1-1 Valid Address, or a
lat/lon/altitude.  Both routing mechanisms will need to be supported for
the foreseeable future.  

# Routing databases using 9-1-1 Valid Addresses or lat/lon/altitude as
keys must both be available to all entities needing to route 9-1-1 calls

# A database, originally derived from the current MSAG must be made
available to validate street addresses.  This database is called the
9-1-1 Address Validation database

# A 9-1-1 valid address is defined as an address with a subset of the
fields in the NENA XML address format, which when looked up in the 9-1-1
Address Validation database, yields exactly one record.

# The fields in the 9-1-1 Address Validation database must be used as
they are defined in the relevant NENA standard, including use of the
Street suffix, pre and post directionals, etc.  Only USPS abbreviations
will be permitted in suffixes.  No abbreviations are permitted in street
names or community names.  All fields must be populated as appropriate,
including the postal community name, county name, and zipcode.

# i3 must define a process to evolve from the current MSAG to the 9-1-1
Address Validation database

# A postal address may be a 9-1-1 valid address if, as stated in
requirement 4, a query to the 9-1-1 Address Validation Database with the
postal address yields exactly one record

# A current MSAG address may be a 9-1-1 valid address if the fields are
fully populated as described in requirement 5 (with respect to, for
example, mandatory use of street suffix and pre/post directionals, only
standard USPS abbreviations permitted, etc.)

# The PSAP must have access to all of contents of the 9-1-1 address
validation database.