ps://author-tools.ietf.org/api/iddiff?doc_1=draft-ietf-opsawg-teas-attachment-circuit&url_2=https://boucadair.github.io/attachment-circuit-model/draft-ietf-opsawg-teas-attachment-circuit.txt
>
>
>
> See more context inline, fwiw.
>
>
>
> Cheers,
>
> Med
>
>
nks for the review.
>
>
>
> All good suggestions. I went with all of the suggestions, except the refs:
> https://author-tools.ietf.org/api/iddiff?url_1=https://boucadair.github.io/simple-ipfix-fixes/draft-ietf-opsawg-ipfix-fixes.txt&url_2=https://boucadair.github.io/simple-ipfix-fixes/Do
This draft seems to be about a pretty generic tabular database remote
interface. I didn't read it super closely but it seems to so general
as to have almost no binding with what open switch is about, although
I'm sure with the right tables having the right rows and columns, you
can indeed control a
it.txt
> .
>
> Cheers,
> Med
>
> > -----Message d'origine-
> > De : Donald Eastlake
> > Envoyé : vendredi 10 mai 2024 23:19
> > À : (rtg-...@ietf.org)
> > Cc : Routing Directorate ; draft-ietf-opsawg-
> > teas-attachment-circuit@ietf.or
It may be of interest that in some cases blocks of parameter values in
RFC 9542 and its predecessors back though RFC 5342 are assigned under
a policy called, in these RFCs, "IESG Ratification". This provides for
Expert Review and then, if the Expert approves or is uncertain, the
final decision is m
