John Scudder has entered the following ballot position for
draft-ietf-opsawg-mud-acceptable-urls-11: Discuss
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
Paul Wouters has entered the following ballot position for
draft-ietf-opsawg-mud-acceptable-urls-11: Abstain
When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)
Please
Roman Danyliw via Datatracker wrote:
> ** Section 3.1 While there is an argument that old firmware was
> insecure and should be replaced, it is often the case that the upgrade
> process involves downtime, or can introduce risks due to needed
> evaluations not having been
Hello, WG. The initial minutes from our 119 meeting are now posted:
https://datatracker.ietf.org/doc/minutes-119-opsawg-202403180530/
Thank you to Rob, Adrian, and Jean for your contributions to the proceedings!
Let us know if there are large errors or omissions.
Henk and I are working
Got it. Thank you Thomas!
If some text can be added to clarify this usage of
ingressInterface/egressInterface and
ingressPhysicalInterface/egressPhysicalInterface, that would help the
implementer.
Cheers,
Xiao Min
Original
From: thomas.g...@swisscom.com
To: 肖敏10093570;
Cc:
Hi Mahesh,
(changing the subject as this point is related to a teas WG doc + adding teas
mailing list)
A choice would be intuitive here. However, a case it might be useful to have
both rather than a choice is to handle migration cases. For example, a slice
service was first bound to a very
