Tengfei, Trying to understand you point about " handle Sixtop ADD Response with return code SUCCESS but 0 cells in cellList "
If the response code is SUCCESS, IMO that means option 1. if option 2 is happening (I assume you mean "there is no memory for allocating more cells"), I would expect another return code, no? THomas ________________________________________ Thomas Watteyne, PhD Sr Research Scientist & Innovator, Inria Sr Networking Design Eng, Analog Devices Founder & Advisor, Wattson Elements/Falco Founder & co-lead, UC Berkeley OpenWSN Co-chair, IETF 6TiSCH www.thomaswatteyne.com ________________________________________ > De: "tengfei chang" <[email protected]> > À: "6tisch" <[email protected]> > Envoyé: Lundi 12 Août 2019 08:52:37 > Objet: [6tisch] draft-ietf-6tisch-msf-06 is published > Dear all, > The draft-ietf-6tisch-msf-06 is just published, it mainly resolved what we > discussed during the IETF meeting. > - add rules for celllist > - update the downstream cell adaptation strategy > Right now, there is one issue remained to be resolved and I am not sure what > is > the right solution. So I need suggestions and feedback from you: > - handle Sixtop ADD Response with return code SUCCESS but 0 cells in cellList > There are two possible reason for this situation > 1. the proposed celllist doesn't meet the requirement from neighbor side > 2. there is schedule memory for adding more cells. > For the 1st reason, the node may try to send another 6P request later. > For the 2nd reason, the node may switch to another parent but it's layer > violated. > Any solutions for this case? > Tengfei > -- > Chang Tengfei, > Postdoctoral Research Engineer , Inria > _______________________________________________ > 6tisch mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6tisch
_______________________________________________ 6tisch mailing list [email protected] https://www.ietf.org/mailman/listinfo/6tisch
