Inline (prefaced by [DC])
On Fri, Apr 12, 2024 at 9:07 AM Michael Richardson
wrote:
>
> Hi, Deb, thank you for the comments.
>
> Deb Cooley via Datatracker wrote:
> >
> -
4, 2024 at 8:26 AM Eliot Lear wrote:
> Hi Deb,
>
> On 04.04.2024 13:45, Deb Cooley via Datatracker wrote:
> >
> > Shepherd writeup: It would be nice to enumerate the manufacturers that
> have
> > implemented this concept. The link to 'https://mudmaker.org&#x
and
> keys in our language. I wish you had been available to do the 8520 review
> ;-)
>
> Thanks,
>
>
>
> On 13.04.2024 15:26, Deb Cooley wrote:
>
> Thanks for the site config fix.
>
> 802.1AR you say? No mention of 802.1 in the draft at all. If the PKI
> ru
inline below w/ [DC] I'd like to see the revised draft, once it is
published (recognizing that I'm not blocking publication).
Deb
On Mon, Aug 5, 2024 at 6:58 AM tirumal reddy wrote:
> Hi Deb,
>
> Thanks for the review. Please see inline
>
> On Sun, 4 Aug 2024
For one remaining clarification, inline w/ [DC]
On Fri, Jul 4, 2025 at 6:06 AM Douglas Gash (dcmgash)
wrote:
> Hello Deb,
>
>
>
> Many thanks for taking the time and for the comments and insights.
>
>
>
> Please see inline:
>
>
>
> *From: *Deb Cooley via
top posting
modification and disclosure are not the same. Default deny write still
allows reading, no?
Deb
On Mon, Jul 7, 2025 at 7:24 AM wrote:
> Hi Deb,
>
> Please see inline.
>
> Cheers,
> Med
>
> > -Message d'origine-
> > De : Deb Cooley
c goes
for radius and the other protocols mentioned). It is (academically)
interesting to see which protocols update and evolve on some schedule and
which are set in concrete. Building protocols that allow evolution and
transition is apparently hard (shrug).
Thanks for the time and effort to
I share Ketan's belief that the tacacs+ protocol should be Standards
Track. Now that the security issues have been resolved, then why not
publish a Standards Track RFC that documents the protocol. It would be
easier for developers/implementers and probably operators as the
information on this wid
Deb Cooley 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 refer
Deb Cooley has entered the following ballot position for
draft-ietf-opsawg-mud-tls-15: No Objection
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 refer to
Deb Cooley has entered the following ballot position for
draft-ietf-opsawg-tacacs-tls13-23: No Objection
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 refer
Deb Cooley has entered the following ballot position for
draft-ietf-opsawg-secure-tacacs-yang-13: 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 refer
Deb Cooley has entered the following ballot position for
draft-ietf-opsawg-ipfix-on-path-telemetry-20: No Objection
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
13 matches
Mail list logo
