Thanks Luigi, Alvaro, Luigi’s proposal seems very reasonable to me, we’ll update the text accordingly.
Thanks! Alberto From: Alvaro Retana <[email protected]> Date: Thursday, January 19, 2023 at 3:22 PM To: Alberto Rodriguez-Natal (natal) <[email protected]>, Luigi Iannone <[email protected]> Cc: Vina Ermagan <[email protected]>, JACQUENET Christian INNOV/NET <[email protected]>, Fabio Maino (fmaino) <[email protected]>, Sharon Barkai <[email protected]>, Dino Farinacci <[email protected]>, [email protected] <[email protected]>, Albert Cabellos <[email protected]>, Stefano Secci <[email protected]>, Johnson Leong <[email protected]>, [email protected] <[email protected]>, [email protected] <[email protected]> Subject: Re: AD Review of draft-ietf-lisp-pubsub-09 Hi! Luigi’s suggestion, or something like it, works for me. The problem with pointing to rfc6830 (even as Informative) is that it is an obsolete document. Thanks! Alvaro. On January 19, 2023 at 8:25:50 AM, Luigi Iannone ([email protected]<mailto:[email protected]>) wrote: Hi, On 19 Jan 2023, at 09:18, Alberto Rodriguez-Natal (natal) <[email protected]<mailto:[email protected]>> wrote: Hi Alvaro, Thanks for reviewing the new version! Your comments seem fine to me, we’ll add all your suggestions along with the DE text suggested by Med to -11. Just one comment regarding the reference to 6830. It is there since 9301 does not suggest any default TTL for mappings, but 6830 does (24-hour) and the value is commonly used in deployments. Let me know if it would fine to keep the reference to 6830 in Informative, otherwise no problem in removing it. IMO you do not need a reference to 6830, you can modify the text being generic. The problem of stale mapping arise any long TTL. Instead of : As per Section 6.6.1 of [RFC6830], the default setting for an EID-to- RLOC mapping TTL in the cache is 24 hours. Upon the expiry of that TTL, the xTR checks if these entries are being used and removes any entry that is not being used. The problem with this 24-hour Map- Cache TTL is that (in the absence of PubSub) if a mapp You can put: EID-to-RLOC mappings can have very long TTL, in the order of several hours.. Upon the expiry of that TTL, the xTR checks if these entries are being used and removes any entry that is not being used. The problem with several hours-long Map- Cache TTL is that (in the absence of PubSub) if a mapp What do you think? Ciao L. Thanks! Alberto From: Alvaro Retana <[email protected]<mailto:[email protected]>> Date: Thursday, January 12, 2023 at 8:40 PM To: Alberto Rodriguez-Natal (natal) <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>> Cc: Vina Ermagan <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, Fabio Maino (fmaino) <[email protected]<mailto:[email protected]>>, [email protected]<mailto:[email protected]> <[email protected]<mailto:[email protected]>>, Dino Farinacci <[email protected]<mailto:[email protected]>>, Luigi Iannone <[email protected]<mailto:[email protected]>>, Albert Cabellos <[email protected]<mailto:[email protected]>>, Stefano Secci <[email protected]<mailto:[email protected]>>, Johnson Leong <[email protected]<mailto:[email protected]>>, JACQUENET Christian INNOV/NET <[email protected]<mailto:[email protected]>>, Sharon Barkai <[email protected]<mailto:[email protected]>> Subject: Re: AD Review of draft-ietf-lisp-pubsub-09 On November 6, 2022 at 5:32:47 AM, Alberto Rodriguez-Natal wrote: Alberto: Hi! I've looked at your replies and the diffs using the version -10. I still have a couple of comments in-line -- mostly about the instructions to the designated experts. Please move the text in §8 (Sample PubSub Deployment Experiences) to an appendix and update the reference to rfc6830. I am starting the IETF Last Call. I know that you still have to address Padma's comments -- you can treat them (and mine) as LC comments. Thanks! Alvaro.
_______________________________________________ lisp mailing list [email protected] https://www.ietf.org/mailman/listinfo/lisp
