[Int-dir] Intdir early review of draft-ietf-rtgwg-net2cloud-problem-statement-26

[Benson Muite via Datatracker <[e-mail]>]

Reviewer: Benson Muite
Review result: Ready with Nits

A useful problem statement. Most suggestions below aim to improve clarity.

1) Acronym Cloud Datacenter (DC) used in introduction should appear in first use
and should be used consistently, DC is also used for on prem data center.

2) May want to define GW - gateway?

3) May want to examine for draft-ietf-cdni-additional-footprint-types adding location information,
though in this case geographic coordinates may be better.

4) Perhaps rephrase:
If an organization uses an internal name
   like .internal and then want your services to be available via or
   within some other cloud provider which also uses .internal, then
   collisions might occur.

to

If an organization uses an internal name
   like .internal and then wants your services to be available via or
   within some other cloud provider which also uses .internal, then
   collisions might occur.


5) Cloud probably does not need to be capitalized in every use when not part of a proper name.

6) Some enterprises/institutions who are not cloud providers may have multiple on premises DC
at different sites.  They may also have similar problems.

7) Maybe introduction of section 4 should be changed from:

 For many enterprises with established provide VPNs (e.g., private
   circuits, MPLS-based L2VPN/L3VPN) interconnecting branch offices &
   on-premises data centers, connecting to Cloud services will be a mix
   of different types of networks.

to

 For many enterprises which provide VPNs (e.g., private
   circuits, MPLS-based L2VPN/L3VPN) that interconnect branch offices &
   on-premises data centers, connecting to Cloud services will be a mix
   of different types of networks.

8) May want to explain "Availability Zone" since different cloud providers
may use this term in slightly different manners.

9) It may be helpful to add examples from cloud providers headquartered
outside the USA.

10) The abbreviation TN in Figure 1 is not defined.

11) Perhaps 'Multi-point-to-Point' to  'multi-point-to-point'

12) MPLS (Multiprotocol Label Switching) is not defined in the document.

13) The abbreviation CPE (Customer Premises Equipment?) in section 4.3 is not defined.

14) May want to use "software application" instead of App

15) As a document not aimed at experts, may wish to reference rfc8926

16) Perhaps update

When
   applications in Cloud communicate with on-premises applications, it
   may not be clear where the Cloud applications are located or to
   which VPCs they belong.

to

When
   applications in the cloud communicate with on-premises applications, it
   may not be clear where the cloud applications are located or to
   which VPCs they belong.

17) Perhaps update

   Approach b) creates additional transmission delay plus incurring
   cost when exiting Cloud DCs.

to

   Approach b) creates additional transmission delays and can incur a
   cost when exiting cloud DCs.

18) Geographic location may not be the only consideration for routing traffic
the nearest link may have very poor performance compared to an alternate
more geographically distant link.