Re: [Sidrops] I-D Action: draft-ietf-sidrops-route-server-rpki-light-02.txt

[Aris Lambrianidis <[e-mail]>]

Hello all,

As a quick note, Daniel and I are in Prague, at IETF99. Daniel will be here until Tuesday afternoon and I’ll be here
for the entire week, should you have any concerns, comments, or questions. We’re looking into moving things forward
(read: go for WG Last Call), so we’d appreciate any feedback, in person or by email.

--Aris


> On 11 Apr 2017, at 18:15, Thomas King <[e-mail]> wrote:
> 
> Hi all,
> 
> we have worked on the feedback we received through many channels (e.g. this mailing list):
> - Clarification of the “Security Considerations” section. Please let us know if you think a security issue is not tackled.
> - The feedback told us that different modes of operation for how “invalid” and “not found” routes should be handled needs to be addressed. For this, section “BGP Prefix Origin Validation State Utilized at Route-Servers” was added.
> - House-Keeping (e.g. update references, fix typos)
> 
> Best regards,
> Thomas
> 
> 
> On 11/04/2017, 18:14, "Sidrops on behalf of [e-mail]" <[e-mail] on behalf of [e-mail]> wrote:
> 
> 
>    A New Internet-Draft is available from the on-line Internet-Drafts directories.
>    This draft is a work item of the SIDR Operations of the IETF.
> 
>            Title           : Signaling Prefix Origin Validation Results from a Route Server to Peers
>            Authors         : Thomas King
>                              Daniel Kopp
>                              Aristidis Lambrianidis
>                              Arnaud Fenioux
>    	Filename        : draft-ietf-sidrops-route-server-rpki-light-02.txt
>    	Pages           : 7
>    	Date            : 2017-04-11
> 
>    Abstract:
>       This document defines the usage of the BGP Prefix Origin Validation
>       State Extended Community [RFC8097] to signal prefix origin validation
>       results from a route server to its peers.  Upon reception of prefix
>       origin validation results peers can use this information in their
>       local routing decision process.
> 
> 
> 
>    The IETF datatracker status page for this draft is:
>    https://datatracker.ietf.org/doc/draft-ietf-sidrops-route-server-rpki-light/
> 
>    There are also htmlized versions available at:
>    https://tools.ietf.org/html/draft-ietf-sidrops-route-server-rpki-light-02
>    https://datatracker.ietf.org/doc/html/draft-ietf-sidrops-route-server-rpki-light-02
> 
>    A diff from the previous version is available at:
>    https://www.ietf.org/rfcdiff?url2=draft-ietf-sidrops-route-server-rpki-light-02
> 
> 
>    Please note that it may take a couple of minutes from the time of submission
>    until the htmlized version and diff are available at tools.ietf.org.
> 
>    Internet-Drafts are also available by anonymous FTP at:
>    ftp://ftp.ietf.org/internet-drafts/
> 
>    _______________________________________________
>    Sidrops mailing list
>    [e-mail]
>    https://www.ietf.org/mailman/listinfo/sidrops
> 
> 
> _______________________________________________
> Sidrops mailing list
> [e-mail]
> https://www.ietf.org/mailman/listinfo/sidrops