Hi Brian, On 29 May 2017, at 02:57, Brian E Carpenter <[email protected]> wrote:
>> 3.5.4.3. Discovery Procedures >> >> In 6th para: >> >> The cache mechanism MUST include a lifetime for each entry. The >> lifetime is derived from a time-to-live (ttl) parameter in each >> Discovery Response message. Cached entries MUST be ignored or >> deleted after their lifetime expires. In some environments, >> unplanned address renumbering might occur. In such cases, the >> lifetime SHOULD be short compared to the typical address lifetime and >> a mechanism to flush the discovery cache MUST be implemented. >> >> How can the discovery cache be flushed? > > I think that's completely implementation-dependent, so what can we say? > (In the prototype, it's an API call.) I think you just demonstrated my point that some requirements are not very clear whom they apply to. Passive voice is causing ambiguity here. I think I would like to see more text on what different possible alternatives are and which entities need to implement the MUST. _______________________________________________ Anima mailing list [email protected] https://www.ietf.org/mailman/listinfo/anima
