[cifs-protocol] SR# 117072516091337 :SMB2 ECHO request

Andreas Schneider asn at samba.org
Mon Jul 31 08:18:48 UTC 2017


On Thursday, 27 July 2017 21:25:51 CEST Jeff McCashland wrote:
> Hi Andreas,

Hi Jeff,

> Normally, this type of information would go into the processing rules for
> the Client (Section 3.2). However, the gist of what I explained below is
> that SMB2 doesn't have any rules for the client to process the ECHO
> command. The client is free to use and process ECHO as needed, as long as
> the structure in section 2.2 is met.
> 
> We could add something like:
> 
> 2.2.1.1	SMB2 Packet Header - ASYNC
> SessionId (8 bytes): Uniquely identifies the established session for the
> command. This field MUST be set to 0 for an SMB2 NEGOTIATE Request (section
> 2.2.3) and for an SMB2 NEGOTIATE Response (section 2.2.4). SessionId MAY be
> set to 0 for an SMB2 ECHO Request (section 2.2.28) and for an SMB2 ECHO
> Response (section 2.2.29).
> 
> 2.2.1.2	SMB2 Packet Header - SYNC
> SessionId (8 bytes): Uniquely identifies the established session for the
> command. This field MUST be set to 0 for an SMB2 NEGOTIATE Request (section
> 2.2.3) and for an SMB2 NEGOTIATE Response (section 2.2.4). SessionId MAY be
> set to 0 for an SMB2 ECHO Request (section 2.2.28) and for an SMB2 ECHO
> Response (section 2.2.29).
> 
> Would that be helpful?


I think that's perfect.


Thanks,


	Andreas


-- 
Andreas Schneider                   GPG-ID: CC014E3D
Samba Team                             asn at samba.org
www.samba.org



More information about the cifs-protocol mailing list