We’ll need to figure out what to do about the I-D.sidr-as-migration reference
it’s in the “IESG Dead” state.
I guess s3.2 is going to match whatever updates are made to bgpsec-protocol-14.
spt
On Oct 07, 2015, at 11:32, Chris Morrow wrote:
>
> Howdy WG folks,
>
> I'd prefer a warning in the security considerations section and a
> recommendation to alert the operator.
please. and put this to bed already.
randy
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
Howdy folks,
We'll be in Yokohama in meeting rooms... so we should have agenda items.
Speak up now pls for meeting topics!
-chris
co-chair
___
sidr mailing list
sidr@ietf.org
https://www.ietf.org/mailman/listinfo/sidr
Howdy WG folks!
the adoption call for:
draft-dseomn-sidr-slurm
is long since past, but I think despite the mild reply set, taking the
work on seems acceptable to the WG, let's re-issue a re-named draft
and discuss more on the list.
Authors pls follow the 'publish new draft' process, thanks!
Howdy WG folks,
Please consider this your warning/notice that the WGLC has been started for:
draft-ietf-sidr-bgpsec-overview
Abstract:
"This document provides an overview of a security extension to the
Border Gateway Protocol (BGP) referred to as BGPsec. BGPsec improves
security for