Warren Kumari has entered the following ballot position for
draft-ietf-taps-arch-18: 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
https
Warren Kumari has entered the following ballot position for
draft-ietf-taps-interface-22: Yes
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
https://w
Review is partially done. Another assignment may be needed to complete it.
Reviewer: Benson Muite
Review result: Ready with Issues
I am an assigned INT directorate reviewer for
. These comments were written primarily for
the benefit of the Internet Area Directors. Document editors and shepherd(
Dear Tatuya,
thank you very much for your review and especially for pointing out the
difference between scope and scope zone.
While the text was originally written with “interface scopes” in mind, it makes
particular sense for TAPS to be precise here, as the API can actually
distinguish between
Roman Danyliw has entered the following ballot position for
draft-ietf-taps-interface-22: 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 to
https
Dear Éric,
Many thanks - to you, as well as all the people you mention!
Regarding the “I would appreciate a reply by the authors, esp on issue 1” to
Tatuya Jinmei’s review: working on it :-)
Regarding your other comments (really *all* comments, including all others from
Tatuya Jinmei): I hope
Éric Vyncke has entered the following ballot position for
draft-ietf-taps-interface-22: Yes
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
https://www
Top post replying ;-) and deleting the previous text.
The TAPS I-Ds are all very *neat* and I intend to change my ballot to YES after
a discussion with the relevant ADs this Thursday. Authors are obviously welcome
as observers during the telechat.
I like Brian's distinction between prescriptive
hi Gorry, all,
inlining to switch it up a bit, I suppose...
> On 5 Sep 2023, at 12:44, Gorry Fairhurst wrote:
>
> I also agree with what was threashed out, over quite some time, in the TAPS
> WG. I agree that someone can have a Transport Services system and could
> implement a different API t
I also agree with what was threashed out, over quite some time, in the
TAPS WG. I agree that someone can have a Transport Services system and
could implement a different API to this - if that is what someone
needed. The two are independent in this way, and other SDOs or companies
could in futur
Hi, all,
+1 to everything said in this thread by TAPS folks (and +2 thanks to Michael
for the history).
IMO there’s a pattern of confusion in this discussion between *prescriptive*
and *descriptive* architecture, which I’ve seen before, as the term
“architecture” has been AIUI used in the IETF
Hi, all,
+1 to everything said in this thread by TAPS folks (and +2 thanks to Michael
for the history).
IMO there’s a pattern of confusion in this discussion between *prescriptive*
and *descriptive* architecture, which I’ve seen before, as the term
“architecture” has been AIUI used in the IETF
12 matches
Mail list logo
