Hi Matthew,
Please see comments inline below.
From: Matthew Bocci (Nokia) <matthew.bo...@nokia.com>
Date: Friday, December 16, 2022 at 1:56 AM
To: bess@ietf.org <bess@ietf.org>, Boutros, Sami <sbout...@ciena.com>
Cc: bess-cha...@ietf.org <bess-cha...@ietf.org>
Subject: [**EXTERNAL**] Re: Implementaion status and request for early
allocation of code points for draft-ietf-bess-evpn-geneve
Sami,
Please can you confirm from which ranges in the relevant IANA registries you
want these code points allocated from?
The Geneve Option Class registry is split as follows:
Range [cid:image002.gif@01D91134.013FF2C0]
Registration Procedures [cid:image002.gif@01D91134.013FF2C0]
0x0000-0x00FF
IETF Review
0x0100-0xFEFF
First Come First Served
0xFF00-0xFFFF
Experimental Use
Since this request is form an IETF document, I would assume you mean the IETF
Review space, but please can you confirm?.
Sami: Yes this should be fine.
Also, for the BGP Tunnel encapsulation attribute sub-tlv registry, we have the
following:
Range [cid:image002.gif@01D91134.013FF2C0]
Registration Procedures [cid:image002.gif@01D91134.013FF2C0]
1-63
Standards Action
64-125
First Come First Served
126-127
Experimental Use
128-191
Standards Action
192-252
First Come First Served
253-254
Experimental Use
Again, I assume the expectation is to allocate from the Standards Action range,
but please can you confirm?
Sami: Correct.
Thanks
Matthew
From: Matthew Bocci (Nokia) <matthew.bo...@nokia.com>
Date: Wednesday, 30 November 2022 at 10:06
To: bess@ietf.org <bess@ietf.org>
Cc: bess-cha...@ietf.org <bess-cha...@ietf.org>
Subject: Implementaion status and request for early allocation of code points
for draft-ietf-bess-evpn-geneve
WG,
There was recently consensus to request publication of this draft.
The BESS Working Group has a policy that at least one implementation must exist
before progressing a standards track draft. We therefore must hold this draft
for the time being awaiting any implementations.
Please notify the chairs if you are aware of any implementations.
The authors have also requested early allocation of code points for this draft.
This would be needed for any implementations. Please see the IANA
Considerations section, which is copied here for your convenience.
Thanks
Matthew
8. IANA Considerations
IANA is requested to assign a new option class from the "Geneve
Option Class" registry for the Ethernet option TLV.
Option Class Description Reference
------------ --------------- -------------
XXXX Ethernet option This document
IANA is requested to assign a new BGP Tunnel Encapsulation Attribute
Sub-TLV from the BGP Tunnel Encapsulation Attribute Sub-TLVs
registry.
BGP Tunnel Attribute Sub-TLV Description Reference
---------------------------- ------------------------- -------------
XXXX Geneve tunnel option type This document
From: Boutros, Sami <sbout...@ciena.com>
Date: Wednesday, 23 November 2022 at 15:55
To: iana-cha...@ietf.org <iana-cha...@ietf.org>
Cc: bess-cha...@ietf.org <bess-cha...@ietf.org>
Subject: Request for early allocation
Hi,
Can we please get early allocation from IANA registries requested in.
https://www.ietf.org/archive/id/draft-ietf-bess-evpn-geneve-05.txt
[ietf.org]<https://urldefense.com/v3/__https:/www.ietf.org/archive/id/draft-ietf-bess-evpn-geneve-05.txt__;!!OSsGDw!Pfgh01xM1aFe5Ejhj5kgNxMNbCovTnRTocDjK6pUkVPXBBKGbXYx_vR0HsIyqZlPMaMxK86TijA4tBxXxRwa$>
Thanks,
Sami
_______________________________________________
BESS mailing list
BESS@ietf.org
https://www.ietf.org/mailman/listinfo/bess
