Dear Pascal, Thank you very much for your support and for your comments.
We'll definitely take into account your comments when preparing -05. Cheers, Carles > Dear all > > Sorry for being late. I support the publication of this document at this > time. > Minor comments; > > Section 3.2.2: RFC 8505 updates RFC 6775 and should be referenced instead > for the DAD operation and the formats being used, which are modified. > > > * With RFC 8505 link local addresses are not registered, which is > exactly what you want here, no need to specify it. > * The EUI-64 field is now called ROVR. It is > > > > You may think about recommending an optional support for AP-ND > (draft-ietf-6lo-<https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-08>ap-nd-08<https://tools.ietf.org/html/draft-ietf-6lo-ap-nd-08>)as > well, this provides address security I the mesh. > > All the best, > > Pascal > > From: 6lo <[email protected]> On Behalf Of Gabriel Montenegro > Sent: jeudi 17 janvier 2019 06:00 > To: lo <[email protected]> > Cc: [email protected]; [email protected] > Subject: [6lo] WG last call on draft-ietf-6lo-blemesh-04 > > I'm initiating WG last call on: > > IPv6 Mesh over BLUETOOTH(R) Low Energy using IPSP > https://tools.ietf.org/html/draft-ietf-6lo-blemesh-04 > > This last call will be over on Wednesday January 30. > > This draft was dormant for some time awaiting implementation experience. > That went well and validated the spec, but it is especially important for > the WG to get some new reviews on this document. > > Please express your view (even if it's just "it looks fine") on this > document. > > Thanks, > > Chairs > _______________________________________________ > 6lo mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6lo > _______________________________________________ 6lo mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lo
