<?xml version="1.0" encoding="UTF-8"?>
<reference anchor="I-D.iurman-6man-generic-id" target="https://datatracker.ietf.org/doc/html/draft-iurman-6man-generic-id-01">
   <front>
      <title>Carrying an Identifier in IPv6 packets</title>
      <author initials="J." surname="Iurman" fullname="Justin Iurman">
         <organization>ULiege</organization>
      </author>
      <date month="February" day="4" year="2023" />
      <abstract>
	 <t>   Some recent use cases have a need for carrying an identifier in IPv6
   packets.  While those drafts might perfectly make sense on their own,
   each document requires IANA to allocate a new code point for a new
   option, and so for very similar situations, which could quickly
   exhaust the allocation space if similar designs are proposed in the
   future.  As an example, one might need an 8-bit ID, while another one
   might need a 32-bit, 64-bit or 128-bit ID.  Or, even worse, one might
   need a 32-bit ID in a specific context, while someone else might also
   need a 32-bit ID in another context.  Therefore, allocating a new
   code point for each similar option is probably not the way to go.

	 </t>
      </abstract>
   </front>
   <seriesInfo name="Internet-Draft" value="draft-iurman-6man-generic-id-01" />
   
</reference>
