Paul Wouters has entered the following ballot position for draft-ietf-rtgwg-net2cloud-problem-statement-41: Discuss
When responding, please keep the subject line intact and reply to all email addresses included in the To and CC lines. (Feel free to cut this introductory paragraph, however.) Please refer to https://www.ietf.org/about/groups/iesg/statements/handling-ballot-positions/ for more information about how to handle DISCUSS and COMMENT positions. The document, along with other ballot positions, can be found here: https://datatracker.ietf.org/doc/draft-ietf-rtgwg-net2cloud-problem-statement/ ---------------------------------------------------------------------- DISCUSS: ---------------------------------------------------------------------- I support John's DISCUSS, and also lean towards balloting Abstain, for much of the same reasons John already mentioned. While this might be a useful document for certain people, I do not think this is an IETF document. My view of the world might be different from the authors with respect to requiring BGP to interact with many cloud services. It seems quite common to use VPNs and NATs to tie things together from on-premise to cloud services using VPCs without ever needing BGP at all. On the IPsec part, I find it strange that RFC4535 is mentioned as there is no requirement for shared group keys or multicast support. One would expect each IPsec tunnel to have independent security properties from the other IPsec tunnels between Cloud DCs, on-premise DC and branch locations. I do not believe a one overarching IPsec management solution could tie these various networks together via IPsec. IPsec (IKE) key management for site-to-site connections what all these kind of IPsec connections are are "setup and forget" type deployments requiring no further key management. There is clearly some interesting operations and commercial advise in the document, but it is very much a snapshot that will not age well. I don't think the IETF is where this should be published. _______________________________________________ rtgwg mailing list -- rtgwg@ietf.org To unsubscribe send an email to rtgwg-le...@ietf.org