Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2019-05-16 Thread nusenu
Montgomery, Douglas (Fed): > Our effort to get our new monitor transitioned to a public facing > system ran into a wall for ~35 days. Unfortunately during that time, > the visa of a visiting researcher leading that effort expired. > > We have almost recovered from all of that. Unfortunately,

Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2019-02-15 Thread nusenu
Montgomery, Douglas (Fed): > Our effort to get our new monitor transitioned to a public facing > system ran into a wall for ~35 days. Unfortunately during that time, > the visa of a visiting researcher leading that effort expired. > > We have almost recovered from all of that. Unfortunately,

Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2019-02-15 Thread Montgomery, Douglas (Fed) via NANOG
Cc: rpki-monitor , "nanog@nanog.org" , "Montgomery, Douglas (Fed)" Subject: Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor? Message-ID: <2b8f9b07-27a7-08ba-ac51-afd39b30f...@riseup.net>

Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2019-02-14 Thread nusenu
Sriram, Kotikalapudi (Fed) (2018-09-18):> I also found your analysis very interesting and useful. Thanks for that. > >> What do you think about adding graphs that show the amount of actually >> unreachable prefixes and IP space? (prefix where no alternative >> valid/unknown announcement exists)

Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2018-09-24 Thread Montgomery, Douglas (Fed) via NANOG
Michel, The GoRTR services that cloudflare speaks of below might be an example of an organization positioned to offer the kind of services you suggest. https://blog.cloudflare.com/rpki-details/ dougm -- Doug Montgomery, Manager Internet & Scalable Systems Research @ NIST On 9/18/18, 4:46

RE: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2018-09-18 Thread Michel Py
Doug, > Douglas Montgomery wrote : > You should follow the discussion of draft-ietf-sidrops-validating-bgp-speaker > which proposed standardizing an approach to doing > what you suggest. Many on this thread think that it is a counterproductive > idea to do this. See discussion starting here:

Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2018-09-18 Thread Montgomery, Douglas (Fed)
Michel, First, thanks for your continued support as a taxpayer. Second, in general our mission is limited to supporting the development and promulgation of consensus standards and the development of test / measurement methods and guidance to accelerate their adoption. In particular we are

RE: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2018-09-17 Thread Michel Py
Doug, > Montgomery, Douglas wrote : > The new monitor has significant additions in the areas of diagnostics, and > highlights issues of > interest such as path / customer cone analysis of prefixes that cover invalid > originations. Thanks for all the work. More visibility will help. I have

Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2018-09-17 Thread Sriram, Kotikalapudi (Fed)
Nusenu, I also found your analysis very interesting and useful. Thanks for that. >What do you think about adding graphs that show the amount of actually >unreachable prefixes and IP space? (prefix where no alternative valid/unknown >announcement exists) I am also part of the NIST BGP team.

Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor?

2018-09-17 Thread Montgomery, Douglas (Fed)
& Scalable Systems Research @ NIST From: on behalf of Job Snijders Date: Monday, September 17, 2018 at 12:23 PM To: nusenu Cc: rpki-monitor , "nanog@nanog.org" Subject: Re: [proj-bgp] adding graphs for actually unreachable RPKI INVALID prefixes to RPKI Monitor? On Mon, 17 Sep