Subject: [atoca] Fwd: New Version Notification for draft-barnes-atoca-delivery-01.txt

From: Richard Barnes <[email-masked]>
Date: Tue, 1 Nov 2011 01:34:35 +0100

Dear ATOCA WG,

In order to provide some concrete basis for discussion at the WG meeting in Taipei, Matt, Karen, and I spent a little time over the last week writing some documents.  
<http://tools.ietf.org/html/draft-barnes-atoca-meta>
<http://tools.ietf.org/html/draft-barnes-atoca-delivery>

The idea is for these two documents, together with the ESCAPE document, to describe a basic suite of protocols for ATOCA.  An ATOCA-enabled network would operate and advertise an AMP metadata/registration server and provide ESCAPE-encoded alerts either using LEAP or some other application protocol.  This system is designed to be able to address constrained networks using LEAP for alert delivery, but also to facilitate alerting using SIP or other application-layer constructs.

Chairs: Please consider this a request for agenda time in Taipei to discuss these documents.

Thanks to all,
--Richard

Begin forwarded message:

> From: [email-masked]
> Subject: New Version Notification for draft-barnes-atoca-delivery-01.txt
> Date: October 31, 2011 9:44:01 AM GMT+01:00
> To: [email-masked]
> Cc: [email-masked]
> 
> A new version of I-D, draft-barnes-atoca-delivery-01.txt has been successfully submitted by Richard Barnes and posted to the IETF repository.
> 
> Filename:	 draft-barnes-atoca-delivery
> Revision:	 01
> Title:		 Lightweight Emergency Alerting Protocol (LEAP)
> Creation date:	 2011-10-31
> WG ID:		 Individual Submission
> Number of pages: 9
> 
> Abstract:
>   Emergency alerts need to be delivered reliably from one source to
>   many recipients at once.  TCP is unsuitable for this style of
>   delivery, because the large number of acknowledgements would likely
>   cause network congestion.  This document defines a UDP-based protocol
>   for delivering alerts that supports fragmentation and retransmission
>   for reliability, and allows the sender of a datagram to control
>   whether acknowledgements are sent.
> 
>   Please send feedback to the [email-masked] mailing list.
> 
> 
> 
> 
> The IETF Secretariat