Re: [lisp] WG work items list [WAS: Re: Proposed WG Charter on GitHub]

[Luigi Iannone <[e-mail]>]

Hi Dino, Padma,

The list of milestones I proposed does not have more than 2 item per deadline, which is reasonable to me. 
However, some milestones do indeed refer to several documents like Privacy and Security, Multicast, and mobility.
IMO there is no need to list the detailed documents and if we finish before the schedule this is a plus not a problem.

Since Nov 2023 is in 2 weeks I agree with Padma that there is no need to rush.

The name encoding document was indeed missing, since it is a simple document we can publish it by March 2024.

The update list looks like:

1. November 2023: Submit a LISP Yang model document to the IESG for consideration
2. March 2024: Submit LISP Traffic Engineering document to the IESG for consideration
3. March 2024: Submit LISP Reliable Transport document to the IESG for consideration
4. March 2024: Submit LISP Name Encoding document to the IESG for consideration
5. June 2024 : Submit LISP geo-coordinates to the IESG for consideration
6. June 2024: Submit a LISP NAT Traversal document to the IESG for consideration
7. November 2024: Submit 8111bis to the IESG for consideration
8. November 2024: Submit merged LCAFbis document to the IESG for consideration
9. March 2025: Submit LISP Privacy and Security documents to the IESG for consideration
10. March 2025: Submit 6832bis Proxy XTRs document to the IESG for consideration
11. June 2025: Submit LISP Mobile documents to the IESG for consideration
12. November 2025: Submit Multicast documents to the IESG for consideration
13. March 2026: Submit LISP Applicability document to the IESG for consideration
14. November 2026: Wrap-Up or recharter 
 

Better?

L.


> On Oct 17, 2023, at 01:46, Padma Pillay-Esnault <[e-mail]> wrote:
> 
> 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 <[e-mail] <mailto:[e-mail]>> 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
>> 
>> 
>> 
>> 
>> 
>> 
>>