Re: [emergency-comment] cap 1.2 IPAWS profile comments

[Rex Brooks <rexb@starbourne.com>]

Thanks Harold,

We will post the disposition of all comments collected during this 
Public Review. However, if I recall correctly, this is now covered in 
CAP v1.2 which is in the process of having all comments collected from 
its first 60-Day Public Review addressed. However, we will double check 
this as well as addressing the "000000" geocode.

Best Regards,
Rex Brooks

Harold Price wrote:
> 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
>
>


-- 
Rex Brooks
President, CEO
Starbourne Communications Design
GeoAddress: 1361-A Addison
Berkeley, CA 94702
Tel: 510-898-0670