Re: [babel] No experimental range in the AE registry

Hi,

It's a bit of problem to change the rfc6126bis draft at this point except
to resolve IESG requests or to fix typos or the like...

We could  have use the early allocation procedures in RFC 7120 to allocate
AE codepoints except that rfc6126bis does not set up an IANA registry to
those codepoints.

I assume this is in connection with IPv4 over IPv6. The best thing to do it
seems to me would be to have the draft which adds that also set up the IANA
registry and assign the new AE value, assuming one is needed. So, the IANA
Consideration section of the new draft would include something like the
following:

IANA is requested to create a new registry on the IANA "Babel Routing
Protocol" web page as follows:

Registry Name: Babel AE Values

Registration Procedure: Expert Review

References: [draft-ietf-babel-rfc6126bis] [this document]

AE Value  Address Type      Reference

--------  --------------    -----------------------------

    0      Wildcard         [draft-ietf-babel-rfc6126bis]

    1      IPv4             [draft-ietf-babel-rfc6126bis]

    2      IPv6             [draft-ietf-babel-rfc6126bis]

    3      IPv6 link local  [draft-ietf-babel-rfc6126bis]

    4      IPv4 over IPv6   [this document]

   5-255   unassigned       [this document]

Thanks,
Donald
===============================
 Donald E. Eastlake 3rd   +1-508-333-2270 (cell)
 2386 Panoramic Circle, Apopka, FL 32703 USA
 d3e3e3@gmail.com

On Thu, Mar 12, 2020 at 3:17 PM Dave Taht <dave.taht@gmail.com> wrote:

> no objections, except that I'm dying to learn about what this new
> extension is. :)
>
> but I also note, given the present rate of extension additions to
> babel, I think it would be over a
> hundred years before the various 8 bit spaces was exhausted, and it's
> easier to just grab a number with consent from the group and run with
> it.
>
> On Thu, Mar 12, 2020 at 12:03 PM Markus Stenberg <markus.stenberg@iki.fi>
> wrote:
> >
> > On 12 Mar 2020, at 18.54, Juliusz Chroboczek <jch@irif.fr> wrote:
> > > Théo (in copy of this mail) and myself are currently working on an
> > > exciting new extension to the protocol, which Théo will describe in
> > > another mail.  We have just realised that we have a problem: there's no
> > > experimental range in the AE registry.
> > >
> > > I therefore propose to reserve the AE range 224-254 for experimental
> use
> > > in the next revision of rfc6126bis.  Any objections?  Donald, is that
> okay
> > > at this stage?
> >
> > Sounds like a good idea to me; in general private use / experimental
> ranges should be in pretty much any protocol to decrease likelihood of
> prototyping conflicting later on with IANA assignments.
> >
> > -Markus
> > _______________________________________________
> > babel mailing list
> > babel@ietf.org
> > https://www.ietf.org/mailman/listinfo/babel
>
>
>
> --
> Make Music, Not War
>
> Dave Täht
> CTO, TekLibre, LLC
> http://www.teklibre.com
> Tel: 1-831-435-0729
>