Cake - FQ_codel the next generation
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Cake List <cake@lists.bufferbloat.net>
Subject: [Cake] Fwd: [tsvwg] Collecting new comments about draft-cbs-teas-5qi-to-dscp-mapping
Date: Fri, 10 Jan 2025 07:28:42 -0800	[thread overview]
Message-ID: <CAA93jw5cdemVP+VB_+Vxno8hy+HaWcQ=fhnim-ULyzKaESsyQA@mail.gmail.com> (raw)
In-Reply-To: <DB9PR06MB791562F7088C4FCB17A22ED29E1C2@DB9PR06MB7915.eurprd06.prod.outlook.com>

More QoS markings from the 5G world. It´s quite the list.


---------- Forwarded message ---------
From: LUIS MIGUEL CONTRERAS MURILLO <luismiguel.contrerasmurillo@telefonica.com>
Date: Fri, Jan 10, 2025 at 7:25 AM
Subject: [tsvwg] Collecting new comments about
draft-cbs-teas-5qi-to-dscp-mapping
To: teas@ietf.org <teas@ietf.org>, tsvwg@ietf.org <tsvwg@ietf.org>
Cc: Krzysztof Szarkowicz <kszarkowicz@gmail.com>, Ivan Bykov
<Ivan.Bykov@rbbn.com>


Dear TEAS WG, copying as well TSVWG,



We, the co-authors of draft-5qi-to-dscp, would like to request your
attention to review the latest version of the draft (document is in
[1], the diff is in [2]), which was updated after the comments
received during IETF 120, but not presented during last IETF 121. We
want to keep progressing the work targeting new version for IETF 122.



This draft primarily addresses the problem of maintaining the service
quality of Radio QoS flows in the Transport Network Domain and focuses
on the application of traffic marking in the IETF domain, providing an
example of queue resource allocation in multi-service networks that
simultaneously serve E-UTRAN (LTE), NG-RAN (5G), and disaggregated
O-RAN architectures. The example is provided only for illustration of
the proposed methodology in the draft.



The draft adheres to the guidance provided by both 3GPP and O-RAN on
QoS flow traffic classification, prioritization and marking, and seeks
to explore the feasibility and implications of implementing these
guidelines within the IETF transport domain. This work aims to enhance
interoperability, coexistence and efficiency in network resource
allocation by bridging these architectures. In no way, the draft does
not impose nor expect any change in either 3GPP nor O-RAN sides. The
scope is only IETF concerns.



We appreciate your time and consideration, and we look forward to your
critical evaluation and constructive feedback.



Best regards,



Ivan, Krzysztof and Luis



[1] https://datatracker.ietf.org/doc/html/draft-cbs-teas-5qi-to-dscp-mapping-03

[2] https://author-tools.ietf.org/iddiff?url1=draft-cbs-teas-5qi-to-dscp-mapping-02&url2=draft-cbs-teas-5qi-to-dscp-mapping-03&difftype=--html




________________________________

Este mensaje y sus adjuntos se dirigen exclusivamente a su
destinatario, puede contener información privilegiada o confidencial y
es para uso exclusivo de la persona o entidad de destino. Si no es
usted. el destinatario indicado, queda notificado de que la lectura,
utilización, divulgación y/o copia sin autorización puede estar
prohibida en virtud de la legislación vigente. Si ha recibido este
mensaje por error, le rogamos que nos lo comunique inmediatamente por
esta misma vía y proceda a su destrucción.

The information contained in this transmission is confidential and
privileged information intended only for the use of the individual or
entity named above. If the reader of this message is not the intended
recipient, you are hereby notified that any dissemination,
distribution or copying of this communication is strictly prohibited.
If you have received this transmission in error, do not read it.
Please immediately reply to the sender that you have received this
communication in error and then delete it.

Esta mensagem e seus anexos se dirigem exclusivamente ao seu
destinatário, pode conter informação privilegiada ou confidencial e é
para uso exclusivo da pessoa ou entidade de destino. Se não é vossa
senhoria o destinatário indicado, fica notificado de que a leitura,
utilização, divulgação e/ou cópia sem autorização pode estar proibida
em virtude da legislação vigente. Se recebeu esta mensagem por erro,
rogamos-lhe que nos o comunique imediatamente por esta mesma via e
proceda a sua destruição


-- 
Dave Täht CSO, LibreQos

           reply	other threads:[~2025-01-10 15:28 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <DB9PR06MB791562F7088C4FCB17A22ED29E1C2@DB9PR06MB7915.eurprd06.prod.outlook.com>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/cake.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAA93jw5cdemVP+VB_+Vxno8hy+HaWcQ=fhnim-ULyzKaESsyQA@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=cake@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox