Hi, my support to this document, the split was necessary as the BBR draft was too long with two very differentiated parts.
regards, Xavi 2016-12-05 16:30 GMT+01:00 Pascal Thubert (pthubert) <[email protected]>: > As editor I support the adoption ; > > > > This draft is extracted from a WG document for a better separation of > roles, updating RFC 6775 vs. new backbone router (6BBR) operations. > > There were discussions on the new text about the link model, these are now > resolved by saying that the link model is not changed but the (positive) > consequences are better understood. > > Also a backward compatibility section was added that was missing in the > 6BBR WG doc from which this text is extracted. > > > > This split clarifies greatly the situation for the updates on ND that are > being done at 6lo with backbone router and AP ND, and componentizes the > work that is left to be done. > > > > Cheers, > > > > Pascal > > > > > > *From:* 6lo [mailto:[email protected]] *On Behalf Of *Gabriel > Montenegro > *Sent:* samedi 3 décembre 2016 02:02 > *To:* [email protected] > *Cc:* Samita Chakrabarti <[email protected]> > *Subject:* [6lo] Working Group adoption call for > draft-thubert-6lo-rfc6775-update > > > > All, > > > > Following up on the WG hum for support in Seoul, this starts a 6lo Working > Group adoption call for draft-thubert-6lo-rfc6775-update-01. > > > > https://datatracker.ietf.org/doc/draft-thubert-6lo-rfc6775-update/ > > > > Please send your opinion (for or against) to the mailing list on adopting > this document as a 6lo WG document. This call will end at 00:00 UTC on > December 16, 2016. > > > > Regards, > > > > Gabriel > > _______________________________________________ > 6lo mailing list > [email protected] > https://www.ietf.org/mailman/listinfo/6lo > >
_______________________________________________ 6lo mailing list [email protected] https://www.ietf.org/mailman/listinfo/6lo
