Subject: [sidr] Fwd: New draft waiting for approval: draft-ietf-sidr-delta-protocol

From: Sandra Murphy <[email-masked]>
Date: Mon, 16 Feb 2015 14:17:52 -0500

This was approved and I've already seen the announcement make it to the list.

--Sandy

Begin forwarded message:

> From: IETF I-D Submission Tool <[email-masked]>
> Subject: New draft waiting for approval: draft-ietf-sidr-delta-protocol
> Date: February 16, 2015 12:00:07 PM EST
> To: "Chris Morrow" <[email-masked]>, "Sandra Murphy" <[email-masked]>
> 
> 
> Hi,
> 
> Chair approval is needed for posting of draft-ietf-sidr-delta-protocol-00.
> 
> To approve the draft, go to this URL (note: you need to login to be able to approve):
>  https://datatracker.ietf.org/submit/status/66706/e0a4b2bdec39e3eda5dfd9b77ace1e8e/
> 
>  File name       : draft-ietf-sidr-delta-protocol
>  Revision        : 00
>  Submission date : 2015-02-16
>  Group           : Secure Inter-Domain Routing
> 
>  Title           : RPKI Repository Delta Protocol
>  Document date   : 2015-02-16
>  Pages           : 18
>  File size       : 45.1 KB
> 
>  Submitter       : Tim Bruijnzeels <[email-masked]>
> 
>  Abstract        :    In the Resource Public Key Infrastructure (RPKI), certificate
>   authorities publish certificates, including end entity certificates,
>   and CRLs to repositories on publication servers.  Relying Parties
>   (RP) retrieve the published information from the repository and MAY
>   store it in a cache.  This document specifies a delta protocol which
>   provides relying parties with a mechanism to query a repository for
>   changes, thus enabling the RP to keep its state in sync with the
>   repository.
> 
> 
> 
>  Authors:
>    Tim Bruijnzeels <[email-masked]>
>    Oleg Muravskiy <[email-masked]>
>    Bryan Weber <[email-masked]>
>    Rob Austein <[email-masked]>
>    David Mandelberg <[email-masked]>
> 
> 
> 
> 
> Best regards,
> 
> 	The IETF Secretariat
> 	through the draft submission service