Le 13/03/2012 19:51, Kerry Lynn a écrit :
Hi Alex,
Thanks for your comment.
I was following the method of generating IIDs used by 6LoWPAN [RFC
4944].
I note that RFC 4291 states in section 2.5.1 "For all unicast
addresses, except those that start with the binary value 000,
Interface IDs are re
Hi Alex,
Thanks for your comment.
I was following the method of generating IIDs used by 6LoWPAN [RFC 4944].
I note that RFC 4291 states in section 2.5.1
"For all unicast addresses, except those that start with the binary value
000, Interface IDs are required to be 64 bits long and to be construc
HEllo,
A side note about this. It is not a request for modification, just a
thought.
I wonder why do we want the Interface Identifier to be of length 64 when
the MS/TP node address seems to be 8bit only.
In a sense, it may be because SLAAC over Ethernet (802) is used to use
64bit IIDs.
But in
Greetings,
The main changes to the WG version of this draft are: a) tweaks that
resulted from the initial public review of the BACnet MS/TP change
proposal, the most significant being the COBS encoding of data and
data crc fields to remove preamble sequences; and b) addition of
two informative app
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IPv6 Maintenance Working Group of the IETF.
Title : Transmission of IPv6 over MS/TP Networks
Author(s) : Kerry Lynn
Jerry Mar
