RE: Seder early review of draft-ietf-rtgwg-net2cloud-problem-statement-41

Hi Linda, Alright, you’ve rejected every one of my review comments as being out-of-scope. I clearly lack the domain knowledge to review this document properly. @Deb Cooley or @Tero Kivinen can you please re-assign this SecDir review to

Re: Seder early review of draft-ietf-rtgwg-net2cloud-problem-statement-41

I know and respect that you asked that a different reviewer be appointed.  However, as Shepherd I am trying to figure out if there is an underlying problem that Linda and I were not able to get at from reading your review. The document is about the problems edge devices encounter inclassifying

RE: [EXTERNAL] Re: Seder early review of draft-ietf-rtgwg-net2cloud-problem-statement-41

Hi Joel, Full disclosure: I’m a crypto and web application guy. I have some exposure to DNS and TCP, but I had to google “BGP” while reading this draft. I tried my best, but I probably don’t have even the minimum required background knowledge to be security reviewing this draft. My (limi

Re: [EXTERNAL] Re: Seder early review of draft-ietf-rtgwg-net2cloud-problem-statement-41

This may help, if I am reading this and the draft correctly, point to a place to clarify.  The assumption is that the communicating parties, while one is hosted locally and one is hosted in the cloud, are actually all acting on behalf of the enterprise.  The enterprise is trying to interconnect

RE: [EXTERNAL] Re: Seder early review of draft-ietf-rtgwg-net2cloud-problem-statement-41

You may own the workload in the cloud (VM, container, lambda function), but you don’t own the infrastructure that it’s running on – that’s the whole point of a public cloud; it’s your job running on someone else’s hardware. In fact, it’s your and several million other people’s jobs running on so