Cluster Details

• draft-ietf-rtgwg-routing-types-17.txt  RFC8294  PUB
• draft-ietf-netmod-yang-tree-diagrams-06.txt  RFC8340  PUB
• draft-ietf-netconf-rfc6536bis-09.txt  RFC8341  PUB
• draft-ietf-netmod-rfc7223bis-03.txt  RFC8343  PUB
• draft-ietf-netmod-rfc7277bis-03.txt  RFC8344  PUB
• draft-ietf-i2rs-yang-network-topo-20.txt  RFC8345  PUB
• draft-ietf-i2rs-yang-l3-topology-16.txt  RFC8346  PUB
• draft-ietf-rtgwg-yang-vrrp-11.txt  RFC8347  PUB
• draft-ietf-netmod-entity-08.txt  RFC8348  PUB
• draft-ietf-netmod-rfc8022bis-11.txt  RFC8349  PUB
• draft-ietf-netmod-rfc6087bis-20.txt  RFC8407  PUB
• draft-ietf-6man-rfc6434-bis-09.txt  RFC8504  PUB
• draft-ietf-netconf-rfc7895bis-07.txt  RFC8525  PUB
• draft-ietf-netconf-nmda-netconf-08.txt  RFC8526  PUB
• draft-ietf-netconf-nmda-restconf-05.txt  RFC8527  PUB
• draft-ietf-netmod-schema-mount-12.txt  RFC8528  PUB
• draft-ietf-rtgwg-ni-model-12.txt  RFC8529  PUB
• draft-ietf-rtgwg-lne-model-10.txt  RFC8530  PUB
• draft-ietf-lime-yang-connection-oriented-oam-model-07.txt  RFC8531  PUB
• draft-ietf-lime-yang-connectionless-oam-18.txt  RFC8532  PUB
• draft-ietf-lime-yang-connectionless-oam-methods-13.txt  RFC8533  PUB
• draft-ietf-bfd-yang-17.txt  RFC9127  PUB
• draft-ietf-pim-yang-17.txt  RFC9128  PUB
• draft-ietf-ospf-yang-29.txt  RFC9129  PUB
• draft-ietf-isis-yang-isis-cfg-42.txt  RFC9130  PUB
• draft-ietf-lsr-yang-isis-reverse-metric-06.txt  RFC9194  PUB

Instructions to author(s):

Please see the AUTH48 notification email from the RFC Editor that contains links to the edited files and other information. To send your approval of or changes for a specific document, please Reply All to the message for the given RFC-to-be in question.

If cluster-wide questions were received, please Reply All to that email so each of the relevant parties may partake in the decision process.

See information below for the status of documents within the cluster that are in AUTH48.

When all approvals for a given document have been received, publication will continue once its normative references have completed the AUTH48 process as well. Upon publication of the cluster, this AUTH48 status page will no longer be available.