Re: [dispatch] Feedback request for draft-dispatch-clfc-00

Ted Hardie <ted.ietf@gmail.com> Thu, 24 August 2023 14:58 UTC

Return-Path: <ted.ietf@gmail.com>
X-Original-To: dispatch@ietfa.amsl.com
Delivered-To: dispatch@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 72744C1524A3 for <dispatch@ietfa.amsl.com>; Thu, 24 Aug 2023 07:58:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.105
X-Spam-Level:
X-Spam-Status: No, score=-2.105 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_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, 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=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 1m6htFK3O8wX for <dispatch@ietfa.amsl.com>; Thu, 24 Aug 2023 07:58:58 -0700 (PDT)
Received: from mail-yw1-x1130.google.com (mail-yw1-x1130.google.com [IPv6:2607:f8b0:4864:20::1130]) (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 A270BC14CE39 for <dispatch@ietf.org>; Thu, 24 Aug 2023 07:58:53 -0700 (PDT)
Received: by mail-yw1-x1130.google.com with SMTP id 00721157ae682-59231a1ca9eso40420827b3.1 for <dispatch@ietf.org>; Thu, 24 Aug 2023 07:58:53 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1692889132; x=1693493932; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=J9UiUVeLpGuQempbUjZKEO+RVZofxo7uh37blNMF0YI=; b=qG8C+DxInvMkSWk7113boeFXArJqDW/gkVgvw0xYuohb3JDsZt6E0PECeVzIs3c5w7 gvF5tBcp/WjgODPSSvV+0mCV0ZOW5MkYUTbMwDG32ernPy/is5JJ26Ku/MupLjJkZD5J CYnHd9urb/vQ8ytXdF0ybuozcpIOev9IUfevddINzZr3Yc1DeeV0dGfiu3zunNyngDnj s1cUTELG/C3xvzmJFJnRvdfD5VNJZcK55m/dSHWA4hPxazmPFC/seb2eOk48szbJa6zG TGkY6Y6hP4JloZz/AQv+65ezltInCb7XCirhAVrerafdtqoNRFjkShZNJB8v4bpf9mkQ m60Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1692889132; x=1693493932; 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=J9UiUVeLpGuQempbUjZKEO+RVZofxo7uh37blNMF0YI=; b=LXlPY56WEjVovGVkkohCv5BAdQKAcJcLgPOnYQH+0COuSuO3CrcTPro3rgI0fc9jSC IzcsvafRZqHoUMfQJghhKbdUJfroIpEDYraQRq9VyIoPgo1Mt2M3g5hbbxiovCj6gDIE Ga/yGizltSDTJJrYJ7seNQOMAonaT1J+3Bcj1q2nd5S7pxh/ODPFwjEa+Y4gPCVehLGL 5Gh8rQoUMk91jsF5O7wVFCzoPszgb8QNEpQa0HVpGbnFgiMpKfni6KmWaDB5TFbSeGKh eE5cMMILuETovsj96FZFedqrMmWJSSIwDaUM/danvOyX8zP2kTQZ8yzx10uqDyD0SdrZ pzDQ==
X-Gm-Message-State: AOJu0Yyk52CPVy6yA+0Qiv/T4ZbC/uusQgd17lag3VwHSQX2pW2pmOvV eQ1E6riJsTwj/4OdOxsCFoFsTN+7vtiV3zsRAMskzAWqhjo=
X-Google-Smtp-Source: AGHT+IFo3eqbMmunsOIQaxNk/9Yn8lLJCyWBWT5ClMKY4OXJTi1aASEkLX4loqYRNp22uWGOz9cvhY/df3BnlHsxfyE=
X-Received: by 2002:a0d:ea14:0:b0:589:db22:bfd6 with SMTP id t20-20020a0dea14000000b00589db22bfd6mr15414280ywe.40.1692889131846; Thu, 24 Aug 2023 07:58:51 -0700 (PDT)
MIME-Version: 1.0
References: <01C621FC-6AFC-4C36-A410-4D58E40CE466@cnic.cn> <CA+9kkMBTro4HcenrvXU1uOvfjXJjBVUJNRrc_BwsbA5p4n1eMA@mail.gmail.com> <C802729C-9BC7-43CD-AEE9-CD8AB15520CD@cnic.cn>
In-Reply-To: <C802729C-9BC7-43CD-AEE9-CD8AB15520CD@cnic.cn>
From: Ted Hardie <ted.ietf@gmail.com>
Date: Thu, 24 Aug 2023 15:58:25 +0100
Message-ID: <CA+9kkMAR-JWPic_S0LXLyzhzLDm3e5Cpy+AyZ+JxMGObzrRCow@mail.gmail.com>
To: WH Y <yangwanghong@cnic.cn>
Cc: "dispatch@ietf.org" <dispatch@ietf.org>
Content-Type: multipart/alternative; boundary="0000000000005910c20603ac7719"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dispatch/8VWS-BaGV7G13wrM4P0RFwY6Kc4>
Subject: Re: [dispatch] Feedback request for draft-dispatch-clfc-00
X-BeenThere: dispatch@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: DISPATCH Working Group Mail List <dispatch.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dispatch>, <mailto:dispatch-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dispatch/>
List-Post: <mailto:dispatch@ietf.org>
List-Help: <mailto:dispatch-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dispatch>, <mailto:dispatch-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 24 Aug 2023 14:58:59 -0000

Hi Wanghong,

Thank you for this clarification.  I think this means that you would have
to approach the groups that standardize the messages for the transports
that you intend to carry the message.  So, the group within 3GPP that
manages the standardization of GTP-U messages.  Unfortunately, I think what
you would have to do is write a document for each of those contexts giving
the syntax for that context.

You may be able to write a more general document describing the motivation
for that approach.  I could see that being published with the IETF's
transport area, but it would be informational, rather than a standards
track document.  I would suggest approaching the Transport ADs to see if
they concur with this approach and, if so, to which group they suggest you
bring the document motivating the approach.  CCWG seems like a natural
choice to me, but they could give you better advice.

best regards,

Ted Hardie

On Thu, Aug 24, 2023 at 3:15 PM WH Y <yangwanghong@cnic.cn> wrote:

> Hello Ted,
>
>     Thanks for your concern!  Yes the information report is independent
> from data transmission.
>
>     There are two reasons: (1) The on-the-fly transmission scheme, such as
> the classic ACK packet header carrying method, is likely to encounter
> congestion situations where information cannot be promptly returned.  (2)
> In  4. Information Transmission and Processing of the draft, we demonstrate
> the existing technologies that can be utilized. Within the 5G network,
> there is GTP-U tunnel between UPF node (deployed in the DC egress) and base
> station (serving as the access point). The new GTP message can be securely
> and rapidly transmitted through this tunnel.
>
>
> Best regards
>
> Wanghong Yang
>
> ---- Replied Message ----
> From Ted Hardie<ted.ietf@gmail.com> <ted.ietf@gmail.com>
> Date 08/24/2023 10:51
> To WH Y<yangwanghong@cnic.cn> <yangwanghong@cnic.cn>
> Cc dispatch@ietf.org<dispatch@ietf.org> <dispatch@ietf.org>
> Subject Re: [dispatch] Feedback request for draft-dispatch-clfc-00
> Dear Wanghong,
>
> Thanks for sharing your work.  If I read this correctly:
>
>
> This document defines a new message type MSG_TYPE_APINFO to transmit the
> transmission capability information of the access point. Note that this
> information is only transmitted between the access point and the DC egress.
>
> you need to pass information outside of the flow (the TCP or QUIC stream
> carrying the holographic data).  Is that correct?
>
> regards,
>
> Ted
>
> On Thu, Aug 24, 2023 at 12:31 AM WH Y <yangwanghong@cnic.cn> wrote:
>
>> Dear Dispatch WG,
>>
>>
>>   We proposed a new draft on the bursty traffic collisions issue in
>> real-time interactive video applications (such as cloud VR). This draft
>> introduces our global flow control mechanism for concurrent bursty flows in
>> the edge network. The egress of a data center can collaborate with wireless
>> access points to prevent concurrent flows from getting into the network,
>> thus guaranteeing a low transmission delay and decreasing network load.
>>
>>
>>     Therefore, we designed a new message type for access network status
>> reports. We also provided an example of how the egress of a data center can
>> control every flow based on the message. You can find more details at
>> https://www.ietf.org/archive/id/draft-dispatch-clfc-00.html.
>>
>>
>>   Does this work align with the interests and objectives of the Dispatch
>> WG? If it does, we expect any feedback for improving our draft.
>>
>>
>>
>>   This is my first trial to propose a standard draft so I apologize in
>> advance for any improper behavior.
>>
>>
>>    Thank you and look forward to your guidance.
>>
>>
>> Best Regards,
>>
>> Wanghong Yang
>>
>>
>> ---------Draft Abstract----------------
>> Bursty concurrent streams from holographic applications can cause
>> congestion in wireless access networks, leading to increased delay and QoS
>> issues. The egress server of a data center (DC egress) can regulate
>> outbound network traffic and mitigate congestion if it obtains dynamic
>> information about the wireless access network's queue and capabilities. The
>> document proposes a network-assisted multi-flow transmission control scheme
>> that leverages underlying link state information of access points to
>> perform delay prediction and flow control at the DC egress to alleviate
>> congestion and improve user experience.
>> ---------------------------------------------
>>
>> _______________________________________________
>> dispatch mailing list
>> dispatch@ietf.org
>> https://www.ietf.org/mailman/listinfo/dispatch
>>
>