rfc9354v3.txt   rfc9354.txt 
skipping to change at line 132 skipping to change at line 132
"OPTIONAL" in this document are to be interpreted as described in "OPTIONAL" in this document are to be interpreted as described in
BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all BCP 14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here. capitals, as shown here.
This document uses the following acronyms and terminologies: This document uses the following acronyms and terminologies:
6BBR: 6LoWPAN Backbone Router 6BBR: 6LoWPAN Backbone Router
6LBR: 6LoWPAN Border Router 6LBR: 6LoWPAN Border Router
6LoWPAN: IPv6 over Low-Power Wireless Personal Area Network
6lo: IPv6 over Networks of Resource-constrained Nodes 6lo: IPv6 over Networks of Resource-constrained Nodes
6LoWPAN: IPv6 over Low-Power Wireless Personal Area Network
6LR: 6LoWPAN Router 6LR: 6LoWPAN Router
AMI: Advanced Metering Infrastructure AMI: Advanced Metering Infrastructure
BBPLC: Broadband Power Line Communication BBPLC: Broadband Power Line Communication
Coordinator: A device capable of relaying messages Coordinator: A device capable of relaying messages
DAD: Duplicate Address Detection DAD: Duplicate Address Detection
skipping to change at line 166 skipping to change at line 166
PAN: Personal Area Network PAN: Personal Area Network
PANC: PAN Coordinator, a coordinator that also acts as the primary PANC: PAN Coordinator, a coordinator that also acts as the primary
controller of a PAN controller of a PAN
PLC: Power Line Communication PLC: Power Line Communication
PLC device: An entity that follows the PLC standards and implements PLC device: An entity that follows the PLC standards and implements
the protocol stack described in this document the protocol stack described in this document
RPL: Routing Protocol for Low-Power and Lossy Networks
RA: Router Advertisement RA: Router Advertisement
RPL: Routing Protocol for Low-Power and Lossy Networks
Below is a mapping table of the terminology between [IEEE_1901.2], Below is a mapping table of the terminology between [IEEE_1901.2],
[IEEE_1901.1], [ITU-T_G.9903], and this document. [IEEE_1901.1], [ITU-T_G.9903], and this document.
+=================+=============+===============+===============+ +=================+=============+===============+===============+
| IEEE 1901.2 | IEEE 1901.1 | ITU-T G.9903 | This document | | IEEE 1901.2 | IEEE 1901.1 | ITU-T G.9903 | This document |
+=================+=============+===============+===============+ +=================+=============+===============+===============+
| PAN Coordinator | Central | PAN | PAN | | PAN Coordinator | Central | PAN | PAN |
| | Coordinator | Coordinator | Coordinator | | | Coordinator | Coordinator | Coordinator |
+-----------------+-------------+---------------+---------------+ +-----------------+-------------+---------------+---------------+
| Coordinator | Proxy | Full-Function | Coordinator | | Coordinator | Proxy | Full-Function | Coordinator |
skipping to change at line 538 skipping to change at line 538
updated per [RFC8505]. updated per [RFC8505].
For address registration in mesh-under mode, since all the PLC For address registration in mesh-under mode, since all the PLC
devices are link-local neighbors to the 6LBR, DAR/DAC or EDAR/EDAC devices are link-local neighbors to the 6LBR, DAR/DAC or EDAR/EDAC
messages are not required. A PLC device MUST register its addresses messages are not required. A PLC device MUST register its addresses
by sending a unicast NS message with an ARO or EARO. The by sending a unicast NS message with an ARO or EARO. The
registration status is fed back via the NA message from the 6LBR. registration status is fed back via the NA message from the 6LBR.
4.5. Header Compression 4.5. Header Compression
The compression of IPv6 datagrams within PLC MAC frames refers to IPv6 header compression in PLC is based on [RFC6282] (which updates
[RFC6282], which updates [RFC4944]. Header compression as defined in [RFC4944]). [RFC6282] specifies the compression format for IPv6
[RFC6282], which specifies the compression format for IPv6 datagrams datagrams on top of IEEE 802.15.4; therefore, this format is used for
on top of IEEE 802.15.4, is the basis for IPv6 header compression in compression of IPv6 datagrams within PLC MAC frames. For situations
PLC. For situations when the PLC MAC MTU cannot support the when the PLC MAC MTU cannot support the 1280-octet IPv6 packet, the
1280-octet IPv6 packet, the headers MUST be compressed according to headers MUST be compressed according to the encoding formats
the encoding formats specified in [RFC6282], including the Dispatch specified in [RFC6282], including the Dispatch Header, the
Header, the LOWPAN_IPHC, and the compression residue carried inline. LOWPAN_IPHC, and the compression residue carried inline.
For IEEE 1901.2 and ITU-T G.9903, the IP header compression follows For IEEE 1901.2 and ITU-T G.9903, the IP header compression follows
the instruction in [RFC6282]. However, additional adaptation MUST be the instruction in [RFC6282]. However, additional adaptation MUST be
considered for IEEE 1901.1 since it has a short address of 12 bits considered for IEEE 1901.1 since it has a short address of 12 bits
instead of 16 bits. The only modification is the semantics of the instead of 16 bits. The only modification is the semantics of the
"Source Address Mode" and the "Destination Address Mode" when set as "Source Address Mode" and the "Destination Address Mode" when set as
"10" in Section 3.1 of [RFC6282], which is illustrated as follows. "10" in Section 3.1 of [RFC6282], which is illustrated as follows.
SAM: Source Address Mode: SAM: Source Address Mode:
skipping to change at line 570 skipping to change at line 570
zeros. The following 64 bits are 0000:00ff:fe00:0XXX, where zeros. The following 64 bits are 0000:00ff:fe00:0XXX, where
0XXX are the 16 bits carried inline, in which the first 4 bits 0XXX are the 16 bits carried inline, in which the first 4 bits
are zero. are zero.
If SAC=1: Stateful context-based compression If SAC=1: Stateful context-based compression
10: 16 bits. The address is derived using context information and 10: 16 bits. The address is derived using context information and
the 16 bits carried inline. Bits covered by context the 16 bits carried inline. Bits covered by context
information are always used. Any IID bits not covered by information are always used. Any IID bits not covered by
context information are taken directly from their corresponding context information are taken directly from their corresponding
bits in the 16-bit to IID mapping given by 0000:00ff:fe00:0XXX, bits in the mapping between the 16-bit short address and the
where 0XXX are the 16 bits carried inline, in which the first 4 IID as provided by 0000:00ff:fe00:0XXX, where 0XXX are the 16
bits are zero. Any remaining bits are zero. bits carried inline, in which the first 4 bits are zero. Any
remaining bits are zero.
DAM: Destination Address Mode: DAM: Destination Address Mode:
If M=0 and DAC=0: Stateless compression If M=0 and DAC=0: Stateless compression
10: 16 bits. The first 112 bits of the address are elided. The 10: 16 bits. The first 112 bits of the address are elided. The
value of the first 64 bits is the link-local prefix padded with value of the first 64 bits is the link-local prefix padded with
zeros. The following 64 bits are 0000:00ff:fe00:0XXX, where zeros. The following 64 bits are 0000:00ff:fe00:0XXX, where
0XXX are the 16 bits carried inline, in which the first 4 bits 0XXX are the 16 bits carried inline, in which the first 4 bits
are zero. are zero.
If M=0 and DAC=1: Stateful context-based compression If M=0 and DAC=1: Stateful context-based compression
10: 16 bits. The address is derived using context information and 10: 16 bits. The address is derived using context information and
the 16 bits carried inline. Bits covered by context the 16 bits carried inline. Bits covered by context
information are always used. Any IID bits not covered by information are always used. Any IID bits not covered by
context information are taken directly from their corresponding context information are taken directly from their corresponding
bits in the 16-bit to IID mapping given by 0000:00ff:fe00:0XXX, bits in the mapping between the 16-bit short address and the
where 0XXX are the 16 bits carried inline, in which the first 4 IID as provided by 0000:00ff:fe00:0XXX, where 0XXX are the 16
bits are zero. Any remaining bits are zero. bits carried inline, in which the first 4 bits are zero. Any
remaining bits are zero.
4.6. Fragmentation and Reassembly 4.6. Fragmentation and Reassembly
The constrained PLC MAC layer provides the functions of fragmentation The constrained PLC MAC layer provides the functions of fragmentation
and reassembly. However, fragmentation and reassembly are still and reassembly. However, fragmentation and reassembly are still
required at the adaptation layer if the MAC layer cannot support the required at the adaptation layer if the MAC layer cannot support the
minimum MTU demanded by IPv6, which is 1280 octets. minimum MTU demanded by IPv6, which is 1280 octets.
In IEEE 1901.1 and IEEE 1901.2, the MAC layer supports payloads as In IEEE 1901.1 and IEEE 1901.2, the MAC layer supports payloads as
big as 2031 octets and 1576 octets, respectively. However, when the big as 2031 octets and 1576 octets, respectively. However, when the
 End of changes. 7 change blocks. 
18 lines changed or deleted 20 lines changed or added

This html diff was produced by rfcdiff 1.48.