Fwd: New Version Notification for draft-iurman-6man-generic-id-00.txt

Justin Iurman <justin.iurman@uliege.be> Sat, 06 August 2022 14:24 UTC

Message-ID: <b46323c1-198e-4d8b-03d1-92ceeb1c18c5@uliege.be>
Date: Sat, 06 Aug 2022 16:24:04 +0200
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:91.0) Gecko/20100101 Thunderbird/91.11.0
Subject: Fwd: New Version Notification for draft-iurman-6man-generic-id-00.txt
References: <165979333181.56337.7726192776637775272@ietfa.amsl.com>
Content-Language: en-US
From: Justin Iurman <justin.iurman@uliege.be>
Cc: draft-ietf-6man-enhanced-vpn-vtn-id@ietf.org, draft-li-6man-topology-id@ietf.org
To: ipv6@ietf.org
In-Reply-To: <165979333181.56337.7726192776637775272@ietfa.amsl.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/ipv6/vg2rGRYeOUBLNOyx79aSWaibUXg>
Precedence: list

Hi 6man,

During our last WG meeting in Philly, we had two controversial 
presentations (i.e., [I-D.draft-ietf-6man-enhanced-vpn-vtn-id] and 
[I-D.draft-li-6man-topology-id]) mainly due to the fact that these 
drafts both create a new option to carry an identifier. We heard quite 
often the "generic" word coming back at the mic, as people in the room 
(or remote) seemed to be worried to waste options that way, for such 
similar options.

And that's exactly why this draft (see below) proposes a new solution to 
carry IDs generically. For that purpose, two new Hop-by-Hop and 
Destination options are defined, called "Generic ID Option" and "Generic 
Context-ID Option". There are some explanations of what both drafts 
mentioned above should do to adapt to this new solution. Comments and 
suggestions are welcome.

Thanks,
Justin

-------- Forwarded Message --------
Subject: New Version Notification for draft-iurman-6man-generic-id-00.txt
Date: Sat, 06 Aug 2022 06:42:11 -0700
From: internet-drafts@ietf.org
To: Justin Iurman <justin.iurman@uliege.be>


A new version of I-D, draft-iurman-6man-generic-id-00.txt
has been successfully submitted by Justin Iurman and posted to the
IETF repository.

Name:		draft-iurman-6man-generic-id
Revision:	00
Title:		Carrying a Generic Identifier in IPv6 packets
Document date:	2022-08-06
Group:		Individual Submission
Pages:		7
URL: 
https://www.ietf.org/archive/id/draft-iurman-6man-generic-id-00.txt
Status: 
https://datatracker.ietf.org/doc/draft-iurman-6man-generic-id/
Html: 
https://www.ietf.org/archive/id/draft-iurman-6man-generic-id-00.html
Htmlized: 
https://datatracker.ietf.org/doc/html/draft-iurman-6man-generic-id


Abstract:
    Some recent use cases seem to have a need for carrying IDs within
    packets.  Two examples are _I-D.draft-ietf-6man-enhanced-vpn-vtn-id_
    and _I-D.draft-li-6man-topology-id_. While they might perfectly make
    sense on their own, each document requires IANA to allocate a new
    code point for a new option, 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 24-bit, 32-bit, or 64-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.

 


The IETF Secretariat

Fwd: New Version Notification for draft-iurman-6m… Justin Iurman