RFC 8163: Transmission of IPv6 over Master-Slave/Token-Passing (MS/TP) Networks
In plain English — editorial summary, not part of the RFC
Master-Slave/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.
Document record
- Document ID
- RFC8163
- Published
- May 2017
- Authors
- K. Lynn; J. Martocci; C. Neilson; S. Donaldson
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- int
- Pages
- 27
- Also known as
- —
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 8168DHCPv6 Prefix-Length Hint IssuesCurrent
May 2017
- RFC 8156DHCPv6 Failover ProtocolCurrent
June 2017
- RFC 8173Precision Time Protocol Version 2 (PTPv2) Management Information BaseCurrent
June 2017
- RFC 8180Minimal IPv6 over the TSCH Mode of IEEE 802.15.4e (6TiSCH) ConfigurationCurrent
May 2017
- RFC 8191Home Network Prefix Renumbering in Proxy Mobile IPv6 (PMIPv6)Current
August 2017
- RFC 8127Mobile Access Gateway Configuration Parameters Controlled by the Local Mobility AnchorCurrent
August 2017
- RFC 8200Internet Protocol, Version 6 (IPv6) SpecificationUpdated
July 2017
- RFC 8201Path MTU Discovery for IP version 6Current
July 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?