[Apn] FW: SAN presentation at Intarea WG agenda

["Eric Vyncke (evyncke)" <[e-mail]>]

Dear CATS WG, INT-AREA WG, APN mailing list members,

Please find below some explanations by Daniel Huang about the relationships between SAN and CATS/APN. Daniel gave me his permission for this forwarding.

Regards,

-éric

From: "[e-mail]" <[e-mail]>
Date: Tuesday, 28 March 2023 at 11:23
To: Eric Vyncke <[e-mail]>
Cc: "[e-mail]" <[e-mail]>, "[e-mail]" <[e-mail]>
Subject: Re: FW: [Int-area] SAN presentation at Re: Intarea WG agenda


Hi Eric,

Please see my reply in line in BLUE.

Thank you for your suggestions and comments.

Look forward to talk to you at the session of this afternoon in intarea WG,

BR,

Daniel Huang

黄光平 huangguangping



标准团队/有线规划部 Wireline architecture team./Wireline Product R&D Institute


[cid:[e-mail]8F60]
[cid:[e-mail]8F60]
南京市雨花区软件大道50号中兴通讯2号楼
R&D Building, ZTE Corporation Software Road No.50,
Yuhua District, Nanjing, P..R.China, 210012
M: [phone]<tel:+86%2013770311052>
E: [e-mail]
www.zte.com.cn<http://www.zte.com.cn/>
Original

From: Int-area <[e-mail]> on behalf of "Eric Vyncke (evyncke)" <evyncke=[e-mail]>
Date: Monday, 27 March 2023 at 14:51
To: Internet Area <[e-mail]>
Subject: [Int-area] SAN presentation at Re: Intarea WG agenda

Dear SAN authors,

After quickly browsing through the different SAN IETF drafts, may I suggest being clear in your intarea presentation on Tuesday about:
- how the SAN use cases are different from the use cases of the CATS ([1] aka CAN) drafts ?
D.H>>Use cases upon which SAN is based include that raised and discussed in CATS about routing-based traffic steering in terms of computing resources of multiple cloud sites as well as servcie instances. On top of that, SAN also address the use cases of networking policies tailored for the service requirements.
- how the SAN use of SIL in the network differs from the header discussed in the APN mailing list ?
D.H>>SIL as well as the header in SAN is designed to indicate to both the network and computing site as an interface of SIL-associated service requirements as well as the service resource status. Termial, SAN ingress and egress, and even the cloud site where the service resides might be aware of SIL, so SIL in SAN is an identification of service sharing globally and uniquely semantics rather than within network between ingress and egress. furthermore ,SID in SAN header is a light-weight index of the identified service without any other information such as user, as well as service parameters.
- where is the SIL added/removed to packets
D.H>>SIL is in user data packets, SAN ingress and egress would route and forward the SIL-marked traffic according but would not have to either add or remove it at any occasion.
Looking forward to listening to the SAN presentation,

Regards,

-éric

[1] https://datatracker.ietf.org/wg/cats/about/


From: Int-area <[e-mail]> on behalf of Wassim Haddad <wassim.haddad=[e-mail]>
Date: Sunday, 26 March 2023 at 13:07
To: Internet Area <[e-mail]>
Cc: "[e-mail]" <[e-mail]>
Subject: [Int-area] Intarea WG agenda

Hi,

The Intarea WG meeting agenda is available at: https://datatracker.ietf.org/meeting/116/materials/agenda-116-intarea-01

Presenters, please upload your slides or send a copy to the chairs.


Thanks,
Wassim H.