idnits 2.17.1 draft-ietf-nsis-rmd-09.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** It looks like you're using RFC 3978 boilerplate. You should update this to the boilerplate described in the IETF Trust License Policy document (see https://trustee.ietf.org/license-info), which is required now. -- Found old boilerplate from RFC 3978, Section 5.1 on line 21. -- Found old boilerplate from RFC 3978, Section 5.5, updated by RFC 4748 on line 4420. -- Found old boilerplate from RFC 3979, Section 5, paragraph 1 on line 4390. -- Found old boilerplate from RFC 3979, Section 5, paragraph 2 on line 4397. -- Found old boilerplate from RFC 3979, Section 5, paragraph 3 on line 4403. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 6 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust Copyright Line does not match the current year == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: : 1 bit. When set to "1" it indicates that the resources/bandwidth carried by a tearing RESERVE MUST not be released. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: * the SCOPING flag MUST not be set, meaning that a default scoping of the message is used. Therefore, the QNE Edges MUST be configured as RMD boundary nodes and the QNE Interior nodes MUST be configured as Interior (intermediary) nodes; == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: Furthermore, the "B" (BREAK) QoS-NSLP flag in the end to end RESERVE message MUST not be set and it MUST be unset if it was set, see QoS-NSLP-RMF API described in QoS-NSLP. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: This procedure is applied to all RMD mechanisms that maintain reservation states. If a refresh RESERVE message does not arrive at a QNE Interior node within the refresh time-out period then the resources associated with this message are removed. This soft state behavior provides certain robustness for the system ensuring that unused resources are not reserved for long time. Resources can be removed by an explicit release at any time. However, in the situation that an end-to-end (tear) RESERVE is retransmitted, see Section 5.2.4 in [QoS-NSLP], then this message MUST not initiate an intra-domain (tear) RESERVE message. This is because the RMF values related to the end-to-end (tear) RESERVE message have been already released during the process of the original (initial) end-to-end (tear) RESERVE message. == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'MUST not' in this paragraph: * The object MUST not be included in this message. This is because the QNE Ingress node does not need to receive a response from the QNE Egress node; == Using lowercase 'not' together with uppercase 'MUST', 'SHALL', 'SHOULD', or 'RECOMMENDED' is not an accepted usage according to RFC 2119. Please use uppercase 'NOT' together with RFC 2119 keywords (if that is what you mean). Found 'SHOULD not' in this paragraph: Note that if the values of the and parameters included in the PHR container carried by a intra-domain tear RESERVE(RMD-QOSM) are set as ((=0 and =1) or (=0 and =0) or (=1 and =1)) then the value SHOULD not be compared to the value and the value of the field MUST not be set. Any QNE edge or QNE Interior node that receives the intra-domain tear RESERVE it MUST check the "I" field included in the PHR Container. If the fied is "0" then the traffic class state (PHB) has to be identified, using the parameter, and the the requested resources included in the field have to be released. This can be achieved by subtracting the amount of RMD traffic class requested resources, included in the field, from the total reserved amount of resources stored in the RMD traffic class state. The value of the