Hi Dino The groupings look good!
Some dates look too aggressive Nov 2023: draft-ietf-lisp-geo, draft-ietf-lisp-name-encoding, RFC 8060 and 9306 (Standards Track). We are already there ... As the dates proposed are target dates, i suggest we keep the date of June 2024 but if we can go faster it is all good. thoughts? Similar comment for mobility. Thanks Padma On Mon, Oct 16, 2023 at 4:35 PM Dino Farinacci <farina...@gmail.com> wrote: > > What do you think of putting some major milestones for mobility and > security sections rather than per document? > > I think security is further out compared to mobility. Just because other > groups will have to peer-review the security documents. But good suggestion > and will incldue below the set that go together (IMO). > > So here is what I suggest: > > For June 2024: Mobility documents as a set to IESG, which include: > > draft-ietf-lisp-eid-mobility, draft-ietf-lisp-mn, > draft-ietf-lisp-predictive-rlocs, draft-ietf-lisp-vpn > > And for June 2025: Security documents as a set to IESG, which include: > > draft-ietf-lisp-crypto (RFC8061 to Standards Track), > draft-ietf-lisp-ecdsa-auth, draft-ietf-lisp-eid-anonymity > > And then, not related to what you asked for, to put all LCAF related stuff > in one set: > > For Nov 2023: > > draft-ietf-lisp-geo, draft-ietf-lisp-name-encoding, RFC 8060 and 9306 > (Standards Track) > > What do you think? > > Dino > > > > > > > >
_______________________________________________ lisp mailing list lisp@ietf.org https://www.ietf.org/mailman/listinfo/lisp
