Hi Yatch, thanks for your response. see inline my comments.
Missatge de Yasuyuki Tanaka <[email protected]> del dia dt., 23 d’abr. 2019 a les 10:49: > Hi Xavi, > > Thank you for your reply. > > On 4/22/2019 5:34 PM, Xavi Vilajosana Guillen wrote: > > When node B power cycles loses the last seen seqNum. Its stored value is > then 0 and hence when it receives the request responds with the error and > with the stored last seen seqnum (0). > > > > does it make sense? > > I don't think so... Why doesn't Node B just use SeqNum received from Node > A for its response? > > Node A in Figure 31 would drop the response with SeqNum=0 at 6P layer > because it is not considered as part of the transaction started by the > request with SeqNum=88. > well SeqNum=0 is only possible after a reset or when the node boots. SeqNum will always be different than 0 except for that occasions. So 6P can be aware situation happening in the middle of a transaction. We took that decision as we consider that Node B may have completely lost the state, which is critical. Probably the option you mention would have been also possible but we took that direction. What is the issue you see with this? > Again, the definition of SeqNum is: > > > SeqNum: The sequence number associated with the 6P Transaction. > > Used to match the 6P Request, 6P Response, and 6P Confirmation > > of the same 6P Transaction. > > Best, > Yatch > regards X -- Dr. Xavier Vilajosana Wireless Networks Lab *Internet Interdisciplinary Institute (IN3)Professor* (+34) 646 633 681 [email protected] <[email protected]> http://xvilajosana.org http://wine.rdi.uoc.edu Parc Mediterrani de la Tecnologia Av Carl Friedrich Gauss 5, B3 Building 08860 Castelldefels (Barcelona). Catalonia. Spain [image: Universitat Oberta de Catalunya]
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
