Skip to content

Move from current to obsolete #335

@italobusi

Description

@italobusi

Section 4, paragraph 21

      This revision obsoletes the following identities:
      - of-minimize-agg-bandwidth-consumption;
      - of-minimize-load-most-loaded-link;
      - of-minimize-cost-path-set;
      - lsp-protection-reroute-extra;
      - lsp-protection-reroute.

draft-ietf-netmod-rfc8407bis in Section 4.7 says that:

The status SHOULD NOT be changed from "current" directly to "obsolete". An
object SHOULD be available for at least one year after the publication date
with a "deprecated" status before it is changed to "obsolete".

Yet, this document has clearly done exactly that. Was it not possible to
deprecate the above identities, introduce the new identities, and a year later,
obsolete the identities that were deprecated?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions