search

ietf-tapswg / api-drafts

Architecture, interface, and implementation drafts for the definition of an abstract API for IETF TAPS
Other
23 stars 15 forks source link

Not just "IETF document in the RFC series" #1330

Closed mwelzl closed 11 months ago

mwelzl commented 1 year ago

From the review by Lars Eggert, DISCUSS part:

Section 4.1, paragraph 8

    *  For IETF protocols, the name of a Protocol-specific Property
       SHOULD be specified in an IETF document published in the RFC
       Series.

For IETF protocols, i.e., protocols published on the IETF RFC stream, those names must IMO be also specified in IETF-stream RFCs. I see no reason to let other RFC streams make definitions for IETF protocols.

mwelzl commented 1 year ago

This has been overtaken by events. I still opened the issue, with label "review", to remind us that we need to answer (it's part of the DISCUSS) section of the comment.

Suggested response:

This now reads: "For IETF protocols, the name of a Protocol-specific Property SHOULD be specified in an IETF document published in the RFC Series after IETF review."