Re: [ippm] Zaheduzzaman Sarker's No Objection on draft-ietf-ippm-pam-08: (with COMMENT)

Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com> Fri, 01 December 2023 17:18 UTC

Return-Path: <zahed.sarker.ietf@gmail.com>
X-Original-To: ippm@ietfa.amsl.com
Delivered-To: ippm@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0C86CC14F5E7; Fri, 1 Dec 2023 09:18:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.104
X-Spam-Level:
X-Spam-Status: No, score=-2.104 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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=gmail.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 axFTFdxMs0eo; Fri, 1 Dec 2023 09:17:58 -0800 (PST)
Received: from mail-pj1-x102f.google.com (mail-pj1-x102f.google.com [IPv6:2607:f8b0:4864:20::102f]) (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 33D37C14F5E6; Fri, 1 Dec 2023 09:17:58 -0800 (PST)
Received: by mail-pj1-x102f.google.com with SMTP id 98e67ed59e1d1-2859bde1d62so2329087a91.2; Fri, 01 Dec 2023 09:17:58 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701451078; x=1702055878; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=kk9SurDaERCOKpWx75wyqC1EIS7c6TVyUXK/n2IcJEg=; b=bVJDzktyCYMpbab8zD1dVMpczJgWfpp4lyVIh5+rkfo3Qxyo5VW1y59QEZzUcM0pMK MKP7ecAQmUMxVJf5Mnj2Q34oTEKyDLtsUnbOwZ0ucqjdNDGpvuJ5LcyKUyTBbIRKZPaQ vLKDgAoPDCcTAe5G09AZfmNJbldli1mQ2ww+wAiQqbhOCoxPb7FDCUD8SSRERnon6tQe tjID53fPeb/Mw8Ry8kKNEb7vYHF4UlDz3dOMMaJfoKUmD5u3PNiOBdYXNjvbvo3Ap4xx RLMEnJ+9BZgG7/A1rL748nZRw53CHE/nWXhZbMYcniMWp1r16VDWDbRBw++ogPmqyLmq 7u6A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701451078; x=1702055878; 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=kk9SurDaERCOKpWx75wyqC1EIS7c6TVyUXK/n2IcJEg=; b=sqMB+zhFBOmCO/TeHg1UCcahLmvT8Ho7MGiyIxbIYgv9K4eT8mn6fXHMtW6gfTi6CK JjQ1TV2+RLvdW6bG5nYUlVkYbMIDMnGEMuMIzTxQNMIn91/vBfA6lDPwIOR2/2KMOmE9 SZo6YkIghS7GR0ZvGxE9TA47f631PulzSjx0X6z9TnH2dvdIMEJAs8fUixm71dd26kfl EmQdrDb4dtfFZ7tjK4DL+cG+zrpQDy5HGdKw+U9/zCJuIffgLIBCRYW0Dg53anRuNAMq qX3IaTWe+fBqIf/Dd5SjJDNPNkWrF8JVTCI7ETeu4VosEgtSUBg501hhv2jXZuTHXtz+ TzJw==
X-Gm-Message-State: AOJu0Yy8pfvuTBGTSQZoAukvd2lNpnTobld7yI2c8aMAUlzjr8axgmNe oKhj8bjIvadLmbvGTDEicutLblgrTuS6k0CtdNs=
X-Google-Smtp-Source: AGHT+IG9R6ZuYu1eQe/BKW1qBHOuDPArPBH3qQdQVdH+NYgYG5rcWx0ghT3fMfH9wa/Yf2Pg9WwZ6AavFIULfQ6GDhc=
X-Received: by 2002:a17:90a:1910:b0:280:2652:d43 with SMTP id 16-20020a17090a191000b0028026520d43mr26956992pjg.17.1701451077523; Fri, 01 Dec 2023 09:17:57 -0800 (PST)
MIME-Version: 1.0
References: <170134111839.29898.13104903625912615479@ietfa.amsl.com> <CA+RyBmU+6q-Z4y7sb6pwUwg6NznKkgVmE_3dL232G=JwoTD52A@mail.gmail.com> <CAEh=tcfKRpjWJNdrQJBsGLfazRkGre7=n1Mnnc3mAZ-z-9WyhQ@mail.gmail.com> <CAEh=tcet4ZNbx7p4m1MJ1vjLn-mUkzemewKW_5=1j3GGcXi+fA@mail.gmail.com> <CA+RyBmXsSnDE-oq5qEYxCmRGmL4GJdurtemy7iGVUoY+m=Nx5g@mail.gmail.com>
In-Reply-To: <CA+RyBmXsSnDE-oq5qEYxCmRGmL4GJdurtemy7iGVUoY+m=Nx5g@mail.gmail.com>
From: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Date: Fri, 01 Dec 2023 19:18:36 +0200
Message-ID: <CAEh=tcd=rnP6NTJtrzvv3nHY+MwgB3xJ4aoPX0a+Hs0gtxXXPg@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ippm-pam@ietf.org, IPPM Chairs <ippm-chairs@ietf.org>, IETF IPPM WG <ippm@ietf.org>, Tommy Pauly <tpauly@apple.com>
Content-Type: multipart/alternative; boundary="000000000000141e1f060b75f385"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/HIs2u75hB5Fhdb7SlOHtg3YKr54>
Subject: Re: [ippm] Zaheduzzaman Sarker's No Objection on draft-ietf-ippm-pam-08: (with COMMENT)
X-BeenThere: ippm@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: IETF IP Performance Metrics Working Group <ippm.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ippm>, <mailto:ippm-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ippm/>
List-Post: <mailto:ippm@ietf.org>
List-Help: <mailto:ippm-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ippm>, <mailto:ippm-request@ietf.org?subject=subscribe>
X-List-Received-Date: Fri, 01 Dec 2023 17:18:02 -0000

That's smart and less confusing, I can say as then one will only interpret
the context to which the SLO are defined.

//Zahed


On Fri, Dec 1, 2023, 19:08 Greg Mirsky <gregimirsky@gmail.com> wrote:

> Hi Zahed,
> thank you for the clarification; that helps a lot.
> I agree that "end-to-end service" makes it ambiguous and might be
> interpreted as an invitation to an ocean boiling party. If we apply
> s/end-to-end service levels/service levels/, would it make the text clearer
> for a reader?  Note that "end-to-end latency" will remain in the text. WDYT?
>
> Regards,
> Greg
>
> On Fri, Dec 1, 2023 at 3:56 AM Zaheduzzaman Sarker <
> zahed.sarker.ietf@gmail.com> wrote:
>
>> and yes, when I understand what does "end-to-end" mean here then I can
>> suggest text :-).
>>
>> //Zahed
>>
>> On Fri, Dec 1, 2023 at 12:03 PM Zaheduzzaman Sarker <
>> zahed.sarker.ietf@gmail.com> wrote:
>>
>>> Hi Greg,
>>>
>>> I am still stack on the concept of "end-to-end" here.
>>>
>>> What is the scope of this "end-to-end"? if this is used for a service
>>> which is deployed in the Internet then we might have multiple networks
>>> carrying the flow, to whom the SLO and PAM works then? Very often in Mobile
>>> network the end-to-end means, Mobile edge network - gateway router (UPF) to
>>> the UE, again in ISPs/transit network we can think about end-to-end between
>>> ingress and egress node. In all the cases a flow can be tracked. Hence,
>>> here we need to put some context to the definition of the "end-to-end". I
>>> might be misunderstanding the whole intention here, in that case please
>>> correct me.
>>>
>>> //Zahed
>>>
>>>
>>> On Thu, Nov 30, 2023 at 8:03 PM Greg Mirsky <gregimirsky@gmail.com>
>>> wrote:
>>>
>>>> Hi Zahed,
>>>> thank you for your question. Your question is close to the question
>>>> Roman raised in his review
>>>> <https://mailarchive.ietf.org/arch/msg/ippm/aIYEZqKUUyFNjooQGM8TQE1cwTk/>.
>>>> To address Roman's comment the sentence edited in the working version as
>>>> follows:
>>>> NEW TEXT:
>>>>    This specification introduces a new set of metrics, Precision
>>>>    Availability Metrics (PAM), aimed at capturing end-to-end service
>>>>    levels for a flow, specifically the degree to which the flow complies
>>>>    with the SLOs that are in effect.
>>>> Our intention is to stress that PAM is used to monitor a flow and
>>>> reflects its conformance to the SLOs. A service, in this model, may include
>>>> one or more flows, and hence, each flow might be characterized using PAM
>>>> according to the set of SLOs. Would you suggest any text update to further
>>>> clarify that relationship? I will upload the new version with updates
>>>> addressing all comments received in the course of IESG discussions.
>>>>
>>>> Regards,
>>>> Greg
>>>>
>>>> On Thu, Nov 30, 2023 at 2:45 AM Zaheduzzaman Sarker via Datatracker <
>>>> noreply@ietf.org> wrote:
>>>>
>>>>> Zaheduzzaman Sarker has entered the following ballot position for
>>>>> draft-ietf-ippm-pam-08: No Objection
>>>>>
>>>>> 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-ippm-pam/
>>>>>
>>>>>
>>>>>
>>>>> ----------------------------------------------------------------------
>>>>> COMMENT:
>>>>> ----------------------------------------------------------------------
>>>>>
>>>>> Thanks for working on this specification.
>>>>>
>>>>> Even though I get the SLO idea, but this specification says
>>>>>
>>>>>    Precision Availability Metrics (PAM), aimed at capturing end-to-end
>>>>> service
>>>>>    levels for a flow, specifically the degree to which flows comply
>>>>> with the
>>>>>    SLOs that are in effect.
>>>>>
>>>>> and I am not sure I get how PAM executes on the end-to-end service
>>>>> levels or
>>>>> what does the "end-to-end" mean in this context. I think it would good
>>>>> to
>>>>> clarify that aspect in this document.
>>>>>
>>>>>
>>>>>
>>>>>