Re: [Sidrops] Adoption request of draft-madi-sidrops-rush-02

Melchior Aelmans <melchior@aelmans.eu> Tue, 08 September 2020 16:51 UTC

MIME-Version: 1.0
References: <F4FD13C1-B437-4A94-BD58-A5805067B6DB@rpstir.net>
In-Reply-To: <F4FD13C1-B437-4A94-BD58-A5805067B6DB@rpstir.net>
From: Melchior Aelmans <melchior@aelmans.eu>
Date: Tue, 08 Sep 2020 18:50:52 +0200
Message-ID: <CALxNLBh6pV=6R18b06cJ8QprsuDKN56P=ZGYrkNLJkF5+SOYww@mail.gmail.com>
To: Di Ma <madi@rpstir.net>
Cc: SIDROps Chairs <sidrops-chairs@ietf.org>, Chris Morrow <morrowc@ops-netman.net>, Keyur Patel <keyur@arrcus.com>, SIDR Operations WG <sidrops@ietf.org>, Nathalie Trenaman <nathalie@ripe.net>
Content-Type: multipart/alternative; boundary="000000000000f56ea305aed0236e"
Archived-At: <https://mailarchive.ietf.org/arch/msg/sidrops/4UMMXJijaGW3MJPJfjgqhEo09w8>
Subject: Re: [Sidrops] Adoption request of draft-madi-sidrops-rush-02
Precedence: list

Hi Chairs,

Any word on the ask below? The authors are curious to hear what you think ;)

Thanks and cheers,
Melchior

On Sat, Aug 29, 2020 at 12:27 PM Di Ma <madi@rpstir.net> wrote:

> Chairs,
>
> We authors just update draft-madi-sidrops-rush into v2 re Randy and Job’s
> concern raised in last IETF SIDROPS meeting.
>
> This version articulates in Security Consideration that :
>
> "RUSH is designed to carry out RPKI cache data update from one to another,
> with out-of-band trust established between those cache servers.  That is,
> the scope of RUSH usage is convergent. Cache subscription management might
> be employed to implement cache identification and verification. "
>
> Please consider this mail as the formal request of adoption of
> draft-madi-sidrops-rush-02 as WG item.
>
> Thanks.
>
> Di
> _______________________________________________
> Sidrops mailing list
> Sidrops@ietf.org
> https://www.ietf.org/mailman/listinfo/sidrops
>

[Sidrops] Adoption request of draft-madi-sidrops-… Di Ma
Re: [Sidrops] Adoption request of draft-madi-sidr… Melchior Aelmans