Re: [Babel-users] TLV and sub-TLV space: allocation policy

2014-07-02 Thread Denis Ovsienko
01.07.2014, 17:22, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr: Dear all, In order to get the extension protocol published, I need to define a policy for allocating TLV numbers.  The reviewer has suggested First-Come-First-Served with public reference, but is also willing to accept

Re: [Babel-users] TLV and sub-TLV space: allocation policy

2014-07-02 Thread Juliusz Chroboczek
Specification Required today seems most workable for everybody in foreseeable future, I finally understood it includes Designated Expert, which I suggested in the past. Sorry for not following up at that time, Denis, but we've got different timings -- there's very little energy I can devote to

Re: [Babel-users] TLV and sub-TLV space: allocation policy

2014-07-02 Thread Henning Rogge
On Wed, Jul 2, 2014 at 2:32 PM, Juliusz Chroboczek j...@pps.univ-paris-diderot.fr wrote: I'm open to discussion, but I'm planning 0-127: Specification Required 128-144: Experimental Use 145-254: Specification Required 255: Reserved What do you think about moving Experimental Use

Re: [Babel-users] TLV and sub-TLV space: allocation policy

2014-07-02 Thread Denis Ovsienko
I'm open to discussion, but I'm planning 0-127: Specification Required 128-144: Experimental Use 145-254: Specification Required 255: Reserved The idea about the Experimental range is that it should be easy to decode by sight in a hexdump. Hence the choice of values. It would also be