Hi Qin，
For TS 23.501, TS 29.522, there have been latest version as follows and "h"
means version 17. All of them have been approved by 3GPP plenary in June
2022 thus can be considered stable.
https://www.3gpp.org/ftp/Specs/archive/23_series/23.501/23501-h50.zip
Richard, Yiyue:
I think two relevant 3GPP standard are 3GPP TS 23.501 version 15.3.0 release
15, 3GPP TS 29.522 version 15.3.0 release 15, In 3GPP TS 23.501, there is NEF
architecture,
[cid:image001.png@01D89C2F.D57B1940]
N33 is specified by 3GPP TS 29.522, for C2 component, my impression, it
Hi Richard and Med,
This is Yixue from Tencent who works in 3GPP for 15 years but new to
IETF.___^ . But actually from years ago, even in my Ph. D study, I like
reading some IETF and IRTF drafts and several years ago,I have noticed
ALTO WG in IETF as in Tencent my research and standard
Hi all,
During the weekly ALTO meeting today, we discussed the coming hackathon and
Qin suggested that we send an update to the mailing list on the FTS+ALTO
project, and here is the update:
- In short, if you want to work on ALTO integration with production, open
projects, this can be a
Hi Med,
There are some efforts in 3GPP; the mowie draft discussed related 3GPP
efforts. I will let Tencent team (Yannis, Yixue, Yuhang) to give more info.
I do not believe there are related efforts in W2; that is, shorten the
feedback loop from passthrough-bounce to direct send. Zili can give an
Hi Richard,
Thanks for this information.
Just out of curiosity, are the proposed extensions currently discussed in the
3GPP?
Cheers,
Med
De : alto De la part de Y. Richard Yang
Envoyé : mardi 19 juillet 2022 20:14
À : IETF ALTO
Objet : [alto] Cellular information exposure discussion (Fwd:
Hi ALTO WG,
During the weekly meeting today, the design team discussed about the
document, and suggested that the authors update the WG on a new version of
the MOWIE draft, which was uploaded last week and focuses on cellular
network information exposure to network-aware applications. The links
Many thanks for your comments again.
于2022年7月19日周二 19:42写道：
> Hi Ziyang, all,
>
>
>
> Thank you for the effort put into this document. Really cool to see
> concrete proposals that use ALTO to feed a network intelligence.
>
>
>
> FWIW, you can find some comments to your draft at:
>
>
>
>-
Hi Luis, Sabine, and Xufeng,
Thank you for editing this draft.
FWIW, you may find some comments at:
* pdf:
https://github.com/boucadair/IETF-Drafts-Reviews/raw/master/draft-lcsr-alto-service-functions-01-rev%20Med.pdf
* doc:
Hi Ziyang, all,
Thank you for the effort put into this document. Really cool to see concrete
proposals that use ALTO to feed a network intelligence.
FWIW, you can find some comments to your draft at:
* pdf:
Hi Chongfeng,
Many thanks for all your suggestions. See my responses inline.
On Thu, Jul 14, 2022 at 2:17 PM Chongfeng Xie
wrote:
> Hi，
> Regarding ALTO Logging and Fault Management, it hasn’t been specified in
> draft-ietf-alto-oam-yang, I am thinking whether we should consider the
>
11 matches
Mail list logo
