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

Minh Ngoc Tran <mipearlska1307@dcn.ssu.ac.kr> Mon, 28 August 2023 15:30 UTC

Return-Path: <mipearlska1307@dcn.ssu.ac.kr>
X-Original-To: bmwg@ietfa.amsl.com
Delivered-To: bmwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 45E9EC15107D for <bmwg@ietfa.amsl.com>; Mon, 28 Aug 2023 08:30:16 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.894
X-Spam-Level:
X-Spam-Status: No, score=-6.894 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_NONE=0.001, T_FILL_THIS_FORM_SHORT=0.01, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=dcn-ssu-ac-kr.20221208.gappssmtp.com
Received: from mail.ietf.org ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 27RQiq2q8wBR for <bmwg@ietfa.amsl.com>; Mon, 28 Aug 2023 08:30:14 -0700 (PDT)
Received: from mail-lj1-x236.google.com (mail-lj1-x236.google.com [IPv6:2a00:1450:4864:20::236]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id EE0B0C15109B for <bmwg@ietf.org>; Mon, 28 Aug 2023 08:30:14 -0700 (PDT)
Received: by mail-lj1-x236.google.com with SMTP id 38308e7fff4ca-2bcd7a207f7so49422771fa.3 for <bmwg@ietf.org>; Mon, 28 Aug 2023 08:30:14 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dcn-ssu-ac-kr.20221208.gappssmtp.com; s=20221208; t=1693236613; x=1693841413; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=tGbBfIDrwDR5l3+XzPANXZbdT+Q2N+LkHSppp3RM6z8=; b=N+s6tYgvU6guGmHPTNSuxacWMwsBEOSYgqbe0JHL5SRVOvKTl8eTuO9bnYscP5I/uS rlx8JJ1oWiFBBWklg4yiOuPt0LwzT5//Nm+1O8fGx7ZTTfoX1y82mHkeTYDI600bltWA h1GKKgRg+wlJYuL2mtKADFq4ccQ+OvtwkDp5I+n6US4YQMc3HYn3uhbfky6Bd6FJ6tdc iyLEqhil53Zm8gAt1pqSjP+WzJvacmMY/oYgNuH3C0dO9TNhxEtScQHpILEomTfEI4GN dCKSVx+O5CMeUBLmJBJH6XMUFfuVF8x2FpH/rpLMXqXG69A7xyaMyP1WQtGK7pR6H2et TItQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693236613; x=1693841413; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=tGbBfIDrwDR5l3+XzPANXZbdT+Q2N+LkHSppp3RM6z8=; b=czjzKmtUzI02F0U+yMYle72mGK8fzOe87MuxlCBS5h5Jx2Vy8dhAbI2mlMeyqR3wq/ mx0jcgJ2MT1gz1JhUwOSbhZUxaUjndFFoiVO0Ch7iDhk2XtsTRdvj8ciXnLcWvyL1qFI WX1yHitoQiGdo91811eldqIDjoTppuDJVZV4CalATYV8uKlhpcnPJOaDOtTOVTQIZzYx byA4i7xy3MvAiaI8gNLYxWGdVyGP1OmXuqu+1S7SOUfz82ArB2aBEqu3Iw7uYo0lSZxg jyXJD7ZIXfYaQYnEX3keCKU3GzfQvLI3hoEdk9UQaCS9/JxCyLjVQ362m7moeAxw0sqi WS0w==
X-Gm-Message-State: AOJu0YyML87VgDi943t1jhD3Oj+yJ78P1eVkbXHBpyS/L3lipQXJg/TR sqV21nXuE+r5XdN1qmy8kbHhlxH87Xcdgc5MBsvR
X-Google-Smtp-Source: AGHT+IHjh4lxOFMS1ni4yC370xaLIOPEovnc33oRknMzfGlK61SeLZdDkp606tEWHwJ8xPrp9LiZZo86NktRvOx/rsI=
X-Received: by 2002:a2e:2d12:0:b0:2bc:eb95:15c7 with SMTP id t18-20020a2e2d12000000b002bceb9515c7mr7535322ljt.49.1693236612748; Mon, 28 Aug 2023 08:30:12 -0700 (PDT)
MIME-Version: 1.0
References: <169089105902.61211.2593474937542261581@ietfa.amsl.com> <CAHjU8B2=fTfTZ=LaXp8wPAm7wgkapkut8e0GY7tgcpwYb=ZMzQ@mail.gmail.com> <KL1PR06MB5924A43222CAA942A9B50383E1E0A@KL1PR06MB5924.apcprd06.prod.outlook.com> <BF42801B-C401-4EC0-80B5-2097C5F3CD57@encrypted.net>
In-Reply-To: <BF42801B-C401-4EC0-80B5-2097C5F3CD57@encrypted.net>
From: Minh Ngoc Tran <mipearlska1307@dcn.ssu.ac.kr>
Date: Tue, 29 Aug 2023 00:30:00 +0900
Message-ID: <CAHjU8B0ctf_wgnCsNdkozRqoBc1DbnAdBp=vkEfa81Af8wy=5g@mail.gmail.com>
To: "sbanks@encrypted.net" <sbanks@encrypted.net>
Cc: "Sridhar K. N. Rao" <sridharkn@u.nus.edu>, "bmwg@ietf.org" <bmwg@ietf.org>, "vratko.polak@pantheon.tech" <vratko.polak@pantheon.tech>
Content-Type: multipart/alternative; boundary="000000000000d2ec510603fd5e9c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/bmwg/75wdMmHxE69TRWs6xCEgnUXZFnw>
Subject: Re: [bmwg] New Version Notification for draft-dcn-bmwg-containerized-infra-12.txt
X-BeenThere: bmwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Benchmarking Methodology Working Group <bmwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/bmwg>, <mailto:bmwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/bmwg/>
List-Post: <mailto:bmwg@ietf.org>
List-Help: <mailto:bmwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/bmwg>, <mailto:bmwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 28 Aug 2023 15:30:16 -0000

Hi Sarah,

In the scope paragraph, we tried to explain what the gap is by mentioning
about the unique characteristics of container infra in the following
sentence of that "gap" sentence ("additional benchmarking considerations
which are unique to the containerized infrastructure, which are container
network models and container resources configurations")

If this is not clear enough, we gladly to hear your suggestion.

Regards,
Ngoc

On Mon, Aug 28, 2023 at 11:50 PM sbanks@encrypted.net <sbanks@encrypted.net>
wrote:

> 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> *On Behalf Of *Minh Ngoc Tran
> *Sent:* 01 August 2023 17:45
> *To:* bmwg@ietf.org
> *Cc:* 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>
> 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>, Sridhar Rao <
> srao@linuxfoundation.org>, Tran Minh Ngoc <mipearlska1307@dcn.ssu.ac.kr>,
> Younghan Kim <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
> https://www.ietf.org/mailman/listinfo/bmwg
>
>
>

-- 

__________________________________

*Minh-Ngoc Tran*

*Distributed Cloud and Network lab*

*Soongsil University *

*511 Sangdo-dong Dongjak-gu*

*Seoul, 156-743 Korea*

*TEL : (+82)-2-820-0841 *