> Maybe remove "yet"?
That's better yes. The sentence was updated to include also discovery
methods that are already defined, so to cover both "future" ones and
"existing" ones from other specifications.
> Maybe move your name to the top of the authors list, and mark
yourself as editor?
Ok for me; can do that in the next revision. I looked for any rules
regarding "editor" in the style guide, but it's left up to WG decision.
> Maybe remove your name from Acknowledgements.
As an author, my name doesn't need to appear anymore in Acknowledgements
indeed.
> I am slightly concerned that some reviewers will want a definition of
"circuit proxy".
In Section 2 we import the term from RFC 8995, where it's defined as:
Circuit Proxy:
A stateful implementation of the Join Proxy. This is the assumed
type of proxy.
According to this definition, a stateful Join Proxy is also a Circuit
Proxy, but a stateless Join Proxy is not.
With this reasoning, the use of "circuit proxy" in the abstract is maybe
not fully correct.
> A very very very long time ago (1996?) I wrote an I-D about different
proxy types.
My search found this 1997 one:
https://datatracker.ietf.org/doc/html/draft-richardson-ipsec-traversal-01
It mentions the "virtual circuit" solution type which looks similar.
Esko
On 7/6/2025 12:24 AM, Michael Richardson wrote:
My thanks to Esko for taking over the stick-handling and moving this document
forward.
(not yet specified in this document)
This text implies that it might be specified in *this* document.
Maybe remove "yet"?
Maybe move your name to the top of the authors list, and mark yourself as
editor?
Maybe remove your name from Acknowledgements.
I am slightly concerned that some reviewers will want a definition of
"circuit proxy".
A very very very long time ago (1996?) I wrote an I-D about different proxy
types. I
wish it had gotten published. So long ago, it seems not to be anywhere I can
find.
It seems wikipedia has:
https://en.wikipedia.org/wiki/Circuit-level_gateway
and a number of firewall vendors speak about it, so maybe the term didn't
die.
--
Michael Richardson<[email protected]> . o O ( IPv6 IøT consulting )
Sandelman Software Works Inc, Ottawa and Worldwide
--
*IoTconsultancy.nl* | Email/Teams: [email protected] | +31 6
2385 8339_______________________________________________
Anima mailing list -- [email protected]
To unsubscribe send an email to [email protected]
