Re: [bmwg] New Version Notification for draft-dcn-bmwg-containerized-infra-12.txt

Hi all,
 (My opinions are as a participant, although I think as a WG chair we can do a bit better here too)

	I am not a fan of reading a document that expects me to understand another document. I realize that in this case, I probably should understand both as a reader (generically speaking for all readers here), but a scope that requires me to understand the gaps of another document is a bit of a stretch, and since we know what the gaps are, why not simply call them out? I have no issue with saying that we’ll address the gaps, but then list them. Doing so makes the document significantly more readable and approachable to all. Ngoc, if you want to share what the specific gaps are, I’m happy to propose text, if you need it.

Thank you,
Sarah

> On Aug 28, 2023, at 1:45 AM, Sridhar K. N. Rao <sridharkn@u.nus.edu> wrote:
> 
> Just rephrasing the scope:
> " The primary scope of this document is to fill in the gaps of previous BMWG’s NFV benchmarking consideration works, RFC8172 and RFC8204, when applied to containerized NFV infrastructure. This document investigates additional benchmarking considerations which are unique to the infrastructure designed for running containerized network functions. These additional considerations include container/pod networking models and configuration of resources such as CPU and Memory for containers/pods."
>  
> From: bmwg <bmwg-bounces@ietf.org <mailto:bmwg-bounces@ietf.org>> On Behalf Of Minh Ngoc Tran
> Sent: 01 August 2023 17:45
> To: bmwg@ietf.org <mailto:bmwg@ietf.org>
> Cc: vratko.polak@pantheon.tech <mailto:vratko.polak@pantheon.tech>
> Subject: [bmwg] Fwd: New Version Notification for draft-dcn-bmwg-containerized-infra-12.txt
>  
>  
> - External Email -
>  
> 
> Hi BMWG members, 
>  
> We have updated the draft to explain the scope clearer as requested from ietf 117 bmwg meeting. Briefly, the changes are:
>  
> -  Merge Overview and Introduction section to remove duplicate information.
> -  Remove Benchmarking Experiences Appendixes
> -  Add a Scope section that briefly explain the document's scope in a clear way:
> " The primary scope of this document is to fill in the gap of previous BMWG’s NFV benchmarking consideration works ([RFC8172] and [RFC8204]) when applying to containerized NFV infrastructure. This document investigates additional benchmarking considerations which are unique to the containerized infrastructure, which are container network models and container resources configurations."
> -  Each consideration causes new benchmarking parameters which are unique to container infrastructure. Specify these parameters in each consideration sub-section.
> 
> We would like to hear comments about our updated draft scope, whether it has addressed Vratko's comments in the meeting.
>  
> Sincerely,
> Ngoc
>  
> ---------- Forwarded message ---------
> From: <internet-drafts@ietf.org <mailto:internet-drafts@ietf.org>>
> Date: Tue, Aug 1, 2023 at 8:57 PM
> Subject: New Version Notification for draft-dcn-bmwg-containerized-infra-12.txt
> To: Jangwon Lee <jangwon.lee@dcn.ssu.ac.kr <mailto:jangwon.lee@dcn.ssu.ac.kr>>, Sridhar Rao <srao@linuxfoundation.org <mailto:srao@linuxfoundation.org>>, Tran Minh Ngoc <mipearlska1307@dcn.ssu.ac.kr <mailto:mipearlska1307@dcn.ssu.ac.kr>>, Younghan Kim <younghak@ssu.ac.kr <mailto:younghak@ssu.ac.kr>>
> 
> 
> 
> A new version of I-D, draft-dcn-bmwg-containerized-infra-12.txt
> has been successfully submitted by Tran Minh Ngoc and posted to the
> IETF repository.
> 
> Name:           draft-dcn-bmwg-containerized-infra
> Revision:       12
> Title:          Considerations for Benchmarking Network Performance in Containerized Infrastructures
> Document date:  2023-08-01
> Group:          Individual Submission
> Pages:          25
> URL:            https://www.ietf.org/archive/id/draft-dcn-bmwg-containerized-infra-12.txt
> Status:         https://datatracker.ietf.org/doc/draft-dcn-bmwg-containerized-infra/
> Html:           https://www.ietf.org/archive/id/draft-dcn-bmwg-containerized-infra-12.html
> Htmlized:       https://datatracker.ietf.org/doc/html/draft-dcn-bmwg-containerized-infra
> Diff:           https://author-tools.ietf.org/iddiff?url2=draft-dcn-bmwg-containerized-infra-12
> 
> Abstract:
>    Recently, the Benchmarking Methodology Working Group has extended the
>    laboratory characterization from physical network functions (PNFs) to
>    virtual network functions (VNFs).  Considering the network function
>    implementation trend moving from virtual machine-based to container-
>    based, system configurations and deployment scenarios for
>    benchmarking will be partially changed by how the resource allocation
>    and network technologies are specified for containerized network
>    functions.  This draft describes additional considerations for
>    benchmarking network performance when network functions are
>    containerized and performed in general-purpose hardware.
> 
> 
> 
> 
> The IETF Secretariat
> 
> 
> 
>  
> -- 
> __________________________________
> Minh-Ngoc Tran
> Distributed Cloud and Network lab
> 
> Soongsil University 
> 
> 511 Sangdo-dong Dongjak-gu
> 
> Seoul, 156-743 Korea
> 
> TEL : (+82)-2-820-0841 
> Notice: This email is generated from the account of an NUS alumnus. Contents, views, and opinions therein are solely those of the sender._______________________________________________
> bmwg mailing list
> bmwg@ietf.org <mailto:bmwg@ietf.org>
> https://www.ietf.org/mailman/listinfo/bmwg