Dear all, (Chair hat off.)
I am in favor of adoption. This document is needed to keep the IPv6 over MS/TP specification up to date. Cheers, Carles On Tue, 16 Dec 2025 at 15:18, Carles Gomez Montenegro <[email protected]> wrote: > Dear all, > > Just a reminder that this call for adoption is still open. > > Cheers, > > Shwetha and Carles > > On Tue, 9 Dec 2025 at 22:51, 최영환 <[email protected]> wrote: > >> Dear all, >> >> I support adoption of the document. >> >> Best regards, >> Younghwan Choi >> >> ----------------------------------- >> YOUNGHWAN CHOI, Ph.D. >> Principal Researcher, PEC, ETRI >> Tel +82-42-860-1429 Fax +82-42-860-5404 >> Email [email protected] >> >> >> >> -----Original Message----- >> From: "Shwetha Bhandari via Datatracker" <[email protected]> >> To: <[email protected]>; <[email protected]>; < >> [email protected]>; >> Cc: >> Sent: 2025-12-05 (금) 01:42:56 (UTC+09:00) >> Subject: [6lo] Call for adoption: draft-lynn-6lo-rfc8163-bis-01 (Ends >> 2025-12-18) >> >> >> Subject: Call for adoption: draft-lynn-6lo-rfc8163-bis-01 (Ends >> 2025-12-18) >> >> This message starts a 2-week Call for Adoption for this document. >> >> Abstract: >> Multidrop Serial Bus/Token Passing (MS/TP) is a medium access control >> method for the RS-485 physical layer and is used primarily in >> building automation networks. This specification defines the frame >> format for transmission of IPv6 packets and the method of forming >> link-local and statelessly autoconfigured IPv6 addresses on MS/TP >> networks. It obsoletes RFC 8163. >> >> File can be retrieved from: >> https://datatracker.ietf.org/doc/draft-lynn-6lo-rfc8163-bis/ >> >> Please reply to this message keeping [email protected] in copy by indicating >> whether you support or not the adoption of this draft as a WG document. >> Comments to motivate your preference are highly appreciated. >> >> Authors, and WG participants in general, are reminded of the Intellectual >> Property Rights (IPR) disclosure obligations described in BCP 79 [2]. >> Appropriate IPR disclosures required for full conformance with the >> provisions >> of BCP 78 [1] and BCP 79 [2] must be filed, if you are aware of any. >> Sanctions available for application to violators of IETF IPR Policy can be >> found at [3]. >> >> Thank you. >> [1] https://datatracker.ietf.org/doc/bcp78/ >> [2] https://datatracker.ietf.org/doc/bcp79/ >> [3] https://datatracker.ietf.org/doc/rfc6701/ >> >> >> >> _______________________________________________ >> 6lo mailing list -- [email protected] >> To unsubscribe send an email to [email protected] >> >
_______________________________________________ 6lo mailing list -- [email protected] To unsubscribe send an email to [email protected]
