[tsvwg] Re: Collecting new comments about draft-cbs-teas-5qi-to-dscp-mapping

[[e-mail]]

Hi Ruediger,



De : [e-mail] <[e-mail]>
Envoyé : jeudi 13 mars 2025 13:43
À : [e-mail]
Cc : [e-mail]; [e-mail]; [e-mail]; [e-mail]
Objet : [Teas] Re: Collecting new comments about draft-cbs-teas-5qi-to-dscp-mapping

Hi Luis,

thanks, I've briefly read the draft.

I appreciate, that the examples given show an aggregation of 5QI to DSCPs, and the grouping shown further allows for simple classification on ranges of DSCPs, if that is desired.

The AF Diffserv spec specifies no reordering between AFn1, n2 and n3. If these are all scheduled by a single queue per AF class, that's not an issue. If you assume a single queue per AF class if there's an IP scheduler, then the question is, why different AF values are assigned. If these separate services and re-ordering may appear between them, a note may be useful. I'm not critical to that, I can imagine it's operational practice, if a high number of DSCPs and queues are configured.

I'm not sure about the deployment requirements. Support of QCIs was optional, as well as support of DSCPs. Then mapping between these is getting complex, as no one can tell, whether and which DiffServ PHB and 5Qi is supported (it get's more difficult, if provider interconnection is added). DCSP standard use is limited from my experience, I guess EF, NMS and BE are common. All others may share a PHB across domains, but not a DSCP.  I don't know about the 5QIs. So flexibility remains important (you've picked informational, I think, that's the correct status).

One observation is, you don't mention L4S. Deutsche Telekom operates L4S on 5G SA schedulers in combination with slicing. L4S may be worth a note (please put it out of scope, if you don't want to add text). To me, it seems to be a good example of a standard IETF IP layer QoS congestion avoidance mechanism interworking with 3GPP scheduling by some kind of joint design.

Finally, operation of QoS may follow different preferences. 8 queues per Interface - that's a lot for some router architectures. In the end, I'd expect consumers to be quite unhappy, if their service constantly faces congestion. Looking at that from a planning and operation perspective, if congestion for BE traffic is not standard, then QoS simply results if there are more resources, than load. L4S is an example for a minimalist design - if all traffic was L4S conformant, there'd be just 1 or 2 queues required per network element (Bob and co-authors may contradict, if I'm completely wrong).

Regards,

Ruediger


Von: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>
Gesendet: Montag, 10. März 2025 18:30
An: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>; [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
Cc: Krzysztof Szarkowicz <[e-mail]<mailto:[e-mail]>>; Ivan Bykov <[e-mail]<mailto:[e-mail]>>
Betreff: [tsvwg] Re: Collecting new comments about draft-cbs-teas-5qi-to-dscp-mapping

Dear TSVWG and TEAS participants,

We would like to send a reminder of this request for collecting more comments in respect to draft-cbs-teas-5qi-to-dscp-mapping.

There was some discussion in TSVWG in the past, as part of the following thread:
https://mailarchive.ietf.org/arch/browse/tsvwg/?gbt=1&index=sP0ysaLasJyKvp3-GBZYysiKc3w

It would be great if we could have more reviews and constructive feedback to improve the document after IETF 122.

Thanks in advance,

Best regards

Ivan, Krzysztof and Luis


De: LUIS MIGUEL CONTRERAS MURILLO <[e-mail]<mailto:[e-mail]>>
Enviado el: viernes, 10 de enero de 2025 16:24
Para: [e-mail]<mailto:[e-mail]>; [e-mail]<mailto:[e-mail]>
CC: Krzysztof Szarkowicz <[e-mail]<mailto:[e-mail]>>; Ivan Bykov <[e-mail]<mailto:[e-mail]>>
Asunto: [Teas] Collecting new comments about draft-cbs-teas-5qi-to-dscp-mapping

AVISO/WARNING: Este mail se ha originado fuera de la organización y no se pudo verificar al remitente / This mail was originated outside the organization and the sender could not be verified

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

________________________________

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
____________________________________________________________________________________________________________
Ce message et ses pieces jointes peuvent contenir des informations confidentielles ou privilegiees et ne doivent donc
pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu ce message par erreur, veuillez le signaler
a l'expediteur et le detruire ainsi que les pieces jointes. Les messages electroniques etant susceptibles d'alteration,
Orange decline toute responsabilite si ce message a ete altere, deforme ou falsifie. Merci.

This message and its attachments may contain confidential or privileged information that may be protected by law;
they should not be distributed, used or copied without authorisation.
If you have received this email in error, please notify the sender and delete this message and its attachments.
As emails may be altered, Orange is not liable for messages that have been modified, changed or falsified.
Thank you.