IPv6 packet: Difference between revisions

Content deleted Content added
Hop-by-hop options and destination options: hop-by-hop can be ignored since RFC8200.
Extension headers: hop-by-hop can be ignored by intermediate nodes since RFC8200.
Line 114:
All extension headers are a multiple of 8 octets in size; some extension headers require internal padding to meet this requirement.
 
There are several extension headers defined,<ref name=rfc8200 /> and new extension headers may be defined in the future. Extension headers are to be examined and processed at the packet's destination only, except for ''Hop-by-Hop Options'', which needis tothe beonly processedone atthat everycan intermediatebe nodeeven onchanged theby packet'sintermediate path,nodes. including sending and receiving node. The defined extension headers below are listed in the preferred order, should there be more than one extension header following the fixed header. Note that all extension headers are optional and should only appear at most once, except for the ''Destination Options'' header, which may appear twice.
 
If a node does not recognize a specific extension header, it should discard the packet and send a ''Parameter Problem'' message ([[ICMPv6]] type 4, code 1).<ref name=rfc8200 /> When a Next Header value <tt>0</tt> appears in a header other than the fixed header a node should do the same.