Hi every body,I noticed this issue very long ago, but I always think the
byte order of IPv6 header is big endian.But I'm not so sure for the
payload.If an application or user want to use little endian in the payload
and it has assurance that the recipient knows this,it can use any of
them.Payload is not a specific conception.
But it is better to specify every thing in the RFC.
From: Markku Savela <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
CC: ipv6@ietf.org, [EMAIL PROTECTED], [EMAIL PROTECTED]
Subject: Re: Endianness of IPv6 and payloads
Date: Fri, 15 Sep 2006 00:31:33 +0300
Is thread trying to say the IPv6 *headers* specified in the IPv6 RFC's
leave the byte order of the header fields unspecified? I never noticed
this omission as an implementor.
For payloads, the issue is moot, because IPv6 and IPv4 payloads and
upper layer headers are same (or should always be, even if some
protocols are only used currently with IPv6).
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
--------------------------------------------------------------------
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6
--------------------------------------------------------------------
