Hi Mr. Kang, I believe Jonathan Hui already responded to your question.
Sorry for the delayed response. We had discussions on the new concept of this link at Dublin IETF following Jonathan's draft presentation. If folks still have questions on the new definition of link which covers both single and multihop, this might be a good time to discuss it on the mailing list. Regards, -Samita On Mon, Aug 18, 2008 at 10:17 AM, Chol Su Kang <[EMAIL PROTECTED]> wrote: > Hi Samita, > > I have questions on >> * Define a link that serves 6lowpan common deployment > > Has there been any discussion on this 6lowpan common deployment link? > > Chol Su Kang > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Geoff Mulligan > Sent: Friday, August 15, 2008 2:48 PM > To: Samita Chakrabarti > Cc: [EMAIL PROTECTED]; 6lowpan > Subject: Re: [6lowpan] 6lowpan ND joint-work goals > > So is this correct? Did Samita summarize the guidelines correctly. > > What is the plan for the design team. > > geoff > > On Sun, 2008-08-10 at 17:14 -0700, Samita Chakrabarti wrote: >> Hi All: >> >> Since we are starting to work on the combined ND solution for 6lowpan, >> as one of the members of the ad-hoc ND team, I thought it would be >> very useful to verify our solution guidelines with the working group. >> I am starting with a few bullet points, please check if that meets our >> (6lowpan wg) requirements. Please feel free to suggest modification >> when it makes sense. >> >> ND Design goals: >> >> >> * Neighbor discovery using IPv6 ND protocol or its variant >> * The solution will use unicast/anycast messages to reduce mulitcast >> * The solution should look into minimizing number of total ND messages >> * Initial boot-strapping information and fault-tolerance should be >> addressed if possible >> * This solution must provide methods for IPv6 address allocation in >> 6lowpan nodes >> * Define a link that serves 6lowpan common deployment >> * The design should work with mesh-under(L2) and route-over(L3) > routing >> * The design should be scalable for adding new nodes into the network >> * The solution should also keep in mind that 6lowpan is a low bW > network >> * The ND design may not necessarily address mobility in > boot-strapping >> and address assignment, but it may be extendable to address >> mobility in future. >> * The design will use IPv6 auto-configuration as the main method for >> address assignment; however stateful address configuration will also >> be considered >> >> >> Thanks, >> -Samita >> _______________________________________________ >> 6lowpan mailing list >> [email protected] >> https://www.ietf.org/mailman/listinfo/6lowpan > > _______________________________________________ > 6lowpan mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6lowpan > _______________________________________________ 6lowpan mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lowpan
