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 11:56 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 E43C1C15106F; Fri, 1 Dec 2023 03:56:42 -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 zl9PN5yRl5Ry; Fri, 1 Dec 2023 03:56:39 -0800 (PST)
Received: from mail-pj1-x102c.google.com (mail-pj1-x102c.google.com [IPv6:2607:f8b0:4864:20::102c]) (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 14E6DC14F73E; Fri, 1 Dec 2023 03:56:39 -0800 (PST)
Received: by mail-pj1-x102c.google.com with SMTP id 98e67ed59e1d1-2839b922c18so1842474a91.1; Fri, 01 Dec 2023 03:56:39 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1701431798; x=1702036598; 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=fqzmkKN/Vuom+Kdp1NhvSfhLv4Pkdg+EQmpf/iLMeTc=; b=Acci9sQ/4KQFRhKoCUzcqju9qgIas0L9d9QSEgHqCTtCGO7wbJBwZfNj/JcMjL4XUQ 6EymLEIyxUkP1wwbxBZdU+gBQDjwI5dYc88BUoADMPYJrqzccre4B4o/DMFm4ZkSETz4 6XMUcctKC4QHi/lDSzh2FY2DnbJBdMBgeNX1RQ7soUhZKMjRNam6Lq4XqbRBEdHAb7Bh jGU5Su6wxVRbopuIOA29tPkK0SlGfeeE/qiejTIM+jbSkp7VCTL0J35KddVnWq3R9vA7 SXrvYrq/UVzrOgSDmYsBA/A9Z08OlvzYwf6+o8bzx9D6vIqpwdoydARUyC1Bx2Yo9lvR aDcg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1701431798; x=1702036598; 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=fqzmkKN/Vuom+Kdp1NhvSfhLv4Pkdg+EQmpf/iLMeTc=; b=awC/wD+nrNOGk+rohsK25YN1GHWX9iGzst8IUCSe7BY4quSoENGL+/rttTivuhyhLp 72reCdWKwvHOSNQAFt/06toE+/l2/ZA14z/YPXt0pjjtGZRErqE57g3wUm0arKRFFTi2 4Ss3jbMWV2gQLwU3MYagk3JKH/hWHBwQzVfxsYNvyNYgMtMWaueQO/FtsQP18wakuMxg /IO+Krj43I6Uk67uDK2b7h+Uw2E4z6h56QY7M9n3b3RFw6iYynEJpykdW/4vLKGZoXVM CREFVDHhAC4dkXkAmrre/hK5SBAbzmiHq6llpnRenB7kUEJe3jAsHB8pBYwe1nYReE1m vr6Q==
X-Gm-Message-State: AOJu0YxNJTP4CSnxqpPFa/qh59MQEib4wqgq1lMNbJJuaNa65WsMXhMP Y6MGQXsH33ifkYsQdd8IQj0f5gU2YHKELiGIBck=
X-Google-Smtp-Source: AGHT+IGrYZWLJXSFESmXeohZdBFdpV2v491fYr6bttLrxmesZrdQcpQXWT6evSz9U8zleh09pZ8ImLt6cNHUa1WL/NY=
X-Received: by 2002:a17:90b:1e02:b0:285:adb1:6acb with SMTP id pg2-20020a17090b1e0200b00285adb16acbmr19982800pjb.29.1701431798452; Fri, 01 Dec 2023 03:56:38 -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>
In-Reply-To: <CAEh=tcfKRpjWJNdrQJBsGLfazRkGre7=n1Mnnc3mAZ-z-9WyhQ@mail.gmail.com>
From: Zaheduzzaman Sarker <zahed.sarker.ietf@gmail.com>
Date: Fri, 01 Dec 2023 12:56:27 +0100
Message-ID: <CAEh=tcet4ZNbx7p4m1MJ1vjLn-mUkzemewKW_5=1j3GGcXi+fA@mail.gmail.com>
To: Greg Mirsky <gregimirsky@gmail.com>
Cc: The IESG <iesg@ietf.org>, draft-ietf-ippm-pam@ietf.org, ippm-chairs@ietf.org, ippm@ietf.org, tpauly@apple.com
Content-Type: multipart/alternative; boundary="000000000000f4d4c2060b717565"
Archived-At: <https://mailarchive.ietf.org/arch/msg/ippm/A8GFQ2-kmUUJKJYdl0i8E5EvZ54>
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 11:56:43 -0000

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.
>>>
>>>
>>>
>>>