Refinements to MSG TTL spec during implementation

[ripienaar]

No description provided.

[ripienaar]

I think this is the only deviations so far? But please let me know about others and once you are done implementing we can merge this with all the changes included

[neilalexander]

Notes:

• Keep reject on Nats-TTL with TTLs disabled for client publishes, but allow keeping the header via sources/mirrors, just ignore them
• Ensure LimitsTTL cannot be enabled at the same time as mirroring
• Future option to remove individual headers on a per-source/mirror basis to remove TTLs later if we want

[ripienaar]

OK, so to summarise where we got to, would this be your understanding @neilalexander :

• We will accept Nats-TTL over sources/mirrors always and leave it as is
• If the Source has ttl handling enabled we will process it
• Mirrors may not enable that setting

right?

[neilalexander]

As it stands, AllowMsgTTL can be enabled on a mirror but LimitsTTL cannot be. Otherwise yep, that's right.

[ripienaar]

As it stands, AllowMsgTTL can be enabled on a mirror but LimitsTTL cannot be. Otherwise yep, that's right.

updated with bd022dc to capture these

[Jarema]

LGTM