Hello Hakima,
I'm putting in the RFID as a selection in the draft. I have two
questions:
- Do we need to include various types of RFIDs?
- Can you send good citations for the Normative References?
I have
http://www.acq.osd.mil/log/sci/ait/DoD_Suppliers_Passive_RFID_Info_Guide_v15update.pdf
Hi Charlie,
I am interested in node IDs that can be represented in a DHCPv6 DUID. There is
RFC6355 which encodes a node ID based on DUID-UUID (Universally Unique
IDentifier). AFAICT, the UUID is a 128-bit container formatted per RFC4122
specifications that includes a time portion and a node ID
Hi Charlie,
I guess I have to say “I don’t know” to both questions. MNIDs are a fairly new
subject
for me, and I think others would be better qualified to answer. Just thought I
would
offer what I do know in case it might be of some help.
Thanks - Fred
From: Charles E. Perkins
Hello again folks,
Here is a proposed text for a new paragraph in the Security Considerations:
Some identifiers (e.g., IMSI) are considered to be private
information. If used in the MNID extension as defined in this
document, the packet including the MNID extension should be
Hello folks,
Now we have two kinds of identifiers that could reasonably be
grouped as a type plus subtypes. I could specify this by writing
another section of the new draft that lays out another subtype
field after the MNID subtype field from 4283. I guess it would
be a subsubtype field if we
Thanks.
Thinking about this further, having the RFID subtype is probably going to be
extremely useful for IOT applications. A MAG/MR can potentially register
devices identified with RFID as the NAI; Also, there seems to be some mapping
between 64-bit EPC and IPv6 Identifier, allowing device
