8000 It's OK for an RFC to be updated by several other RFCs · Issue #180 · ietf-tools/idnits · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
10000
It's OK for an RFC to be updated by several other RFCs #180
Open
@rjsparks

Description

@rjsparks

at 5469c26, idnits3 run over https://www.ietf.org/archive/id/draft-ietf-tsvwg-nqb-29.xml reports:

 5  Warning
 └- Code - UPDATES_UPDATED_RFC
 └- Desc - The <rfc> field states that it updates RFC 8325 but it's already updated by RFC RFC8622.
 └- Ref  - https://authors.ietf.org/en/rfcxml-vocabulary#updates
 └- Path - rfc.updates

This is not a valid warning. I suspect it's interpolated from the requirement to warn when a document tries to Obsolete an already Obsoleted RFC. But it's expected that RFCs can be updated by many RFCs (see, e.g., RFC3261).

Also, there's a nit issue in the Desc field at "by RFC RFC622" that probably exists in the check for Obsoleted.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      0