An infinite period should work ok. Thanks.
-----Oprindelig meddelelse----- Fra: Zach Shelby [mailto:z...@sensinode.com] Sendt: on 27-01-2010 15:19 Til: Anders Brandt Cc: 6lowpan Emne: Re: 6LoWPAN-ND - Use of node registration should be optional Anders, On Jan 27, 2010, at 15:13 , Anders Brandt wrote: > Hi Zach et al. > > While not sure what you end up doing in the next revision of ND, I have > got the impression that node registration is mandatory. Here is a micro-summary: The -08 version no longer differentiates Edge Routers and Routers when it comes to registration. Instead, the NR/NC exchange is only made link-locally between a node and the router its default router. That router may be an Edge Router. There is no longer the concept of an Extended LoWPAN or Whiteboard in this draft, and NR messages are not relayed. Yes, this Node Registration must be performed for a node to use a router. This is important because that message exchange builds up the necessary information on both sides for address resolution, unreachability detection and for a node to check that its address is unique. > > I suggest that use of the registration/confirmation mechanism is > optional > so that nodes must use it if a capable ER router is present but nodes > can > run happily without if there is no ER. The last text I saw did not say > so. Like I summarized above, there is no longer an ER role. Every router is capable of answering a registration. This registration is soft, and must be refreshed periodically. But this does not mean an exchange every second or even hour. The current Binding Lifetime field can be from 10 seconds to a week. If we feel that is too short, we could easily extend that up to a month or so. We are also exploring a way for that binding refresh to be possible using other traffic, such as routing protocol signaling between routers, to avoid sending NRs when not necessary. > > > The extreme use case here is the "Home Control starter set" consisting > of a > remote control and three plug-in modules. > The remote control is the master of the network; used for inclusion of > the > three plug-in modules. A unique local IPv6 subnet is communicated to > each > module and then the remote control goes to sleep. > > From this moment the remote control only wakes up when a user presses a > button. > The modules will get the notion of the phrase "in space, no one can hear > you scream"... > Periodic use of node registration does not make sense in this use case. Is it a problem if a node needs to register once a week or month to tell that they are still alive with an NR? We could even make it possible to make an "indefinite binding time" for you if that makes sense in this kind of very limited, fixed case. Zach > > Just my $0.05 > > - Anders -- http://www.sensinode.com http://zachshelby.org - My blog "On the Internet of Things" http://6lowpan.net - New book - "6LoWPAN: The Wireless Embedded Internet" Mobile: +358 40 7796297 Zach Shelby Head of Research Sensinode Ltd. Kidekuja 2 88610 Vuokatti, FINLAND This e-mail and all attached material are confidential and may contain legally privileged information. If you are not the intended recipient, please contact the sender and delete the e-mail from your system without producing, distributing or retaining copies thereof.
_______________________________________________ 6lowpan mailing list 6lowpan@ietf.org https://www.ietf.org/mailman/listinfo/6lowpan
