On Thu, Feb 02, 2017 at 03:02:57PM -0800, Dino Farinacci wrote:
> > I was looking into the procedures to request a LCAF type and
> > realized that there seems to be two LCAF registries on IANA: 'LISP
> > Address Type' [1] and 'LISP LCAF Type' [2]. One is defined by
> > RFC6830 [3] and the other by draft-ietf-lisp-lcaf [4]. The problem
> > is that they define different allocation mechanisms (FCFS vs
> > specification required) for the second half of the LCAF space
> > (128-255). Why do we keep two and which one is the authoritative
> > registry? My guess is that 'LISP Address Type' should be overridden
> > by 'LISP LCAF Type' but wanted to check with the WG. Sorry if this
> > has been pointed out before and I missed the discussion.
>
> Well it really is FCFS after a specification has been written. There
> is really is only one registry. They just were called different names.
> We can fix this in RFC6830bis/RFC6833bis.
>
> And when we do that update these bis RFCs we can point them to RFC8060
> (the LCAF to be RFC soon).
"RFC to be"? It was published 30 minutes ago! :-)
https://www.rfc-editor.org/rfc/rfc8060.txt
Congratulations Dino, thank you for your perseverance in driving this
documenting through the process.
Kind regards,
Job
_______________________________________________
lisp mailing list
lisp@ietf.org
https://www.ietf.org/mailman/listinfo/lisp
