[bess] Secdir telechat review of draft-ietf-bess-bgp-sdwan-usage-20

Stephen Farrell via Datatracker <noreply@ietf.org> Thu, 15 February 2024 16:30 UTC

MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Stephen Farrell via Datatracker <noreply@ietf.org>
To: secdir@ietf.org
Cc: bess@ietf.org, draft-ietf-bess-bgp-sdwan-usage.all@ietf.org, last-call@ietf.org
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <170801460098.63559.14958554152761679042@ietfa.amsl.com>
Reply-To: Stephen Farrell <stephen.farrell@cs.tcd.ie>
Date: Thu, 15 Feb 2024 08:30:01 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/bess/ttrsWK-L1eR1oNd1JdlGRhyx3RQ>
Subject: [bess] Secdir telechat review of draft-ietf-bess-bgp-sdwan-usage-20

Reviewer: Stephen Farrell
Review result: Has Issues

Draft-20 seems to dial-back the call for BGP/TLS, but OTOH adds text in the
security considerations saying that BGP/TLS "is imperative." I'm not sure of
the security pitfalls that might arise if one followed the guidance here whilst
BGP/TLS is still just a non-wg -00 draft (and hence aspirational), but it seems
to me like a possibly dangerous implement.

[bess] Secdir telechat review of draft-ietf-bess-… Stephen Farrell via Datatracker
Re: [bess] Secdir telechat review of draft-ietf-b… Linda Dunbar
Re: [bess] Secdir telechat review of draft-ietf-b… Stephen Farrell
Re: [bess] Secdir telechat review of draft-ietf-b… Linda Dunbar