Hi Matthieu:
We have finished our investigation on your question on MS-FRS1.
The following statement in section 3.3.4.4.3 is not correct
"COMM_LAST_JOIN_TIME MUST be 1."
A doc bug is filed and a change will be made in future release. As such,
COMM_LAST_JOIN_TIME will not always be 1. It is 1 only when a new connection is
being made or a data base recovery is being performed. For all other scenarios,
it is set to the last join time taken from the corresponding connection object.
Your question "what "unknown change orders to the downstream partner based on
the downstream partner version vector." means?" can be best answered by
describing the difference between VVJoin and "simple" join. In case of a
VVJoin, whole IDTable is scanned for the changes that the downstream does not
know about. In case of "simple" join, only Outbound Log object is scanned for
changes that the downstream does not know about.
Please let me know if it answers your question.
Regards,
Obaid Farooqi
Escalation Engineer | Microsoft
Exceeding your expectations is my highest priority. If you would like to
provide feedback on your case you may contact my manager at
[email protected]
-----Original Message-----
From: Obaid Farooqi
Sent: Wednesday, August 31, 2011 2:49 PM
To: '[email protected]'
Cc: [email protected]; [email protected]; MSSolve Case Email
Subject: RE:[REG:111083100373286] FRS clarification about VVJOIN in FRS
Hi Matthieu:
I'll help you with this issue and would be in touch as soon as I have an answer.
Regards,
Obaid Farooqi
Escalation Engineer | Microsoft
Exceeding your expectations is my highest priority. If you would like to
provide feedback on your case you may contact my manager at
[email protected]
-----Original Message-----
From: Matthieu Patou [mailto:[email protected]]
Sent: Tuesday, August 30, 2011 6:09 PM
To: Interoperability Documentation Help; [email protected];
[email protected]
Subject: FRS clarification about VVJOIN in FRS
Hello Dochelp,
I have some problems to understand something in the join process related to
VVJOIN.
In paragraph "3.3.4.4.4 COMM_COMMAND Is CMD_JOINING" we have at the end
After the CMD_JOINED packet is sent:
* If a connection VVJoin needs to be performed, FRS MUST go through the process
specified in the following section.
* If a connection VVJoin does not need to be performed, the upstream partner
MUST send unknown change orders to the downstream partner based on the
downstream partner version vector.
And in paragraph "3.3.4.4.4.1 Connection VVJoin"
FRS MUST perform Connection VVJoin when either of the following conditions is
true:
* P_IN.COMM_LAST_JOIN_TIME is 1.
* Last connection session establishment (Join) time of the outbound connection
is 1.
During VVJoin, the upstream partner MUST send out a CMD_REMOTE_CO packet for
each file
Due to the way FRS1 is redacted I understand that the upstream partner when
receiving a packet with a CMD_JOINING (P_IN) it must check what is described at
3.3.4.4.4.1in order to determine if should do a "simple"
join or a VVJoin. Among the condition to determine if the join should be VVJoin
I have the impression that the condition "P_IN.COMM_LAST_JOIN_TIME is 1." is
always true, as if I understand correctly P_IN referrer to the packet with the
CMD_JOINING command and in paragraph "3.3.4.4.3 COMM_COMMAND Is
CMD_START_JOIN", which describe how the next packet that is to say a packet
with CMD_JOINING, it is said that COMM_LAST_JOIN_TIME must be set to 1. Can you
confirm ?
Also I'd like to understand more what "unknown change orders to the downstream
partner based on the downstream partner version vector." means, and if possible
I'd like to have an example.
Thanks.
Matthieu.
--
Matthieu Patou
Samba Team http://samba.org
Private repo http://git.samba.org/?p=mat/samba.git;a=summary
Microsoft is committed to protecting your privacy. Please read the Microsoft
Privacy Statement for more information.The above is an email for a support case
from Microsoft Corp.REPLY ALL TO THIS MESSAGE or INCLUDE [email protected]
IN YOUR REPLY if you want your response added to the case automatically. For
technical assistance, please include the Support Engineer on the TO: line.
Thank you.
_______________________________________________
cifs-protocol mailing list
[email protected]
https://lists.samba.org/mailman/listinfo/cifs-protocol
