cap 1.2 IPAWS profile comments

[Harold Price <hprice@sagealertingsystems.com>]

1) EAS requires a UTC start time in its protocol.  The dateTime 
element used by CAP has an optional timezone field, the timezone 
isn't required.  A dateTime without a timezone can't be converted 
into an EAS UTC time unless the CAP to EAS converter knows what the 
local time of the originator of the message was.

There is no method within CAP to provide that additional data.

Early recommendations from the EAS vendor community asked that the 
optional timezone be made mandatory in CAP, or at least in the EAS 
profile, otherwise undetectable duplicate messages will result in the 
EAS domain.  The CAP 1.2 IPAWS profile update removed the discussion 
of a mandatory timezone, and I don't see anywhere else where it was 
added.  The timezone, or some way to determine the timezone of the 
originator, is required for CAP to EAS conversion.  This concept 
needs to appear in the document set somewhere.

2)  In the discussion of geocode, "000000" is defined to be all US 
territory.  It should be noted that some legacy EAS equipment does 
not recognize 000000, as it was not in the original FCC referenced 
FIPS document, and the use of 000000 could result in a rejected message.

Regards,
Harold Price
Sage Alerting Systems