Hi Metze,

Thanks for your patience on this question. I am setting up an SMB over QUIC 
repro in my lab environment so that I can debug and determine the significance 
of the Stream ID. I will get back in touch once I have information to share 
with you.

Regards,
Kristian Smith
Support Escalation Engineer | Microsoft® Corporation
Email: kristian.sm...@microsoft.com

-----Original Message-----
From: Kristian Smith <kristian.sm...@microsoft.com> 
Sent: Friday, March 28, 2025 8:37 AM
To: Stefan Metzmacher <me...@samba.org>
Cc: cifs-protocol@lists.samba.org; Microsoft Support <supportm...@microsoft.com>
Subject: RE: [EXTERNAL] MS-SMB2 over QUIC and usage of QUIC streams - 
TrackingID#2503280040007778

[DocHelp to Bcc]

Hi Metze,

Thanks for reaching out with your questions regarding QUIC in MS-SMB2. Case 
2503280040007778 has been created for your inquiries and one of our engineers 
will respond soon.

Regards,
Kristian Smith
Support Escalation Engineer | Microsoft® Corporation
Email: kristian.sm...@microsoft.com

-----Original Message-----
From: Stefan Metzmacher <me...@samba.org> 
Sent: Friday, March 28, 2025 12:11 AM
To: Interoperability Documentation Help <doch...@microsoft.com>
Cc: cifs-protocol@lists.samba.org
Subject: [EXTERNAL] MS-SMB2 over QUIC and usage of QUIC streams

Hi DocHelp,

in MS-SMB2 I can't find any hint on the usage about streams with a QUIC 
connection.

 From captures I see that a Windows client uses stream id 0.
And from various talks and discussions at conferences it seems to be clear that 
only a single stream is used.

But I'm wondering what happens if a peer creates additional streams. How does a 
Windows client behave if that happens?
Will these be ignored?
Will the whole QUIC connection be terminated?
Will the stream id being ignored?
Does a Windows Server only accepts clients using stream id 0?

It would be good to have this documented.

Thanks!
metze

_______________________________________________
cifs-protocol mailing list
cifs-protocol@lists.samba.org
https://lists.samba.org/mailman/listinfo/cifs-protocol

Reply via email to