Hi all,
As I mentioned at IETF 93, I think SLURM
(https://tools.ietf.org/html/draft-dseomn-sidr-slurm-02) is in good
shape for working group adoption. It's a relatively simple solution that
supports two of the use cases from draft-ietf-sidr-lta-use-cases-03, and
it replaces parts of draft-iet
yes, I concur as well.
Steve
This seems correct to me (the proposed change I mean)
At Tue, 25 Aug 2015 15:45:52 -0700 (PDT),
RFC Errata System wrote:
The following errata report has been submitted for RFC7132,
"Threat Model for BGP Path Security".
--
You m
> I think this text should reference RFC6811 (origin validation), not
> RFC6810 (the rpki-rtr protocol).
sigh. the erratum is correct.
randy
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
This seems correct to me (the proposed change I mean)
At Tue, 25 Aug 2015 15:45:52 -0700 (PDT),
RFC Errata System wrote:
>
> The following errata report has been submitted for RFC7132,
> "Threat Model for BGP Path Security".
>
> --
> You may review the report
The following errata report has been submitted for RFC7132,
"Threat Model for BGP Path Security".
--
You may review the report below and at:
http://www.rfc-editor.org/errata_search.php?rfc=7132&eid=4454
--
Type: Editorial
Rep
Hi all,
I wanted to announce newer versions of BGPsec supporting code using
BIRD: bgpsec-bird-client v1.0 and v0.6 of BGPsec support code for
BIRD. They are available as a source tarballs at:
http://bgpsec.tislabs.com
The bgpsec-bird-client application has two main features. It uses the
rpki-
