rfc9748v2.txt | rfc9748.txt | |||
---|---|---|---|---|
skipping to change at line 59 ¶ | skipping to change at line 59 ¶ | |||
Trust Legal Provisions and are provided without warranty as described | Trust Legal Provisions and are provided without warranty as described | |||
in the Revised BSD License. | in the Revised BSD License. | |||
Table of Contents | Table of Contents | |||
1. Introduction | 1. Introduction | |||
2. Existing Registries | 2. Existing Registries | |||
2.1. Reference ID and Kiss-o'-Death Registries | 2.1. Reference ID and Kiss-o'-Death Registries | |||
2.2. Extension Field Types | 2.2. Extension Field Types | |||
2.3. Network Time Security Registries | 2.3. Network Time Security Registries | |||
3. Registry Updates | 3. NTP Registry Updates | |||
3.1. Guidance to Designated Experts | 3.1. Designated Experts | |||
4. IANA Considerations | 4. IANA Considerations | |||
4.1. NTP Reference Identifier Codes | 4.1. NTP Reference Identifier Codes | |||
4.2. NTP Kiss-o'-Death Codes | 4.2. NTP Kiss-o'-Death Codes | |||
4.3. NTP Extension Field Types | 4.3. NTP Extension Field Types | |||
5. Security Considerations | 5. Security Considerations | |||
6. Normative References | 6. Normative References | |||
Acknowledgements | Acknowledgements | |||
Author's Address | Author's Address | |||
1. Introduction | 1. Introduction | |||
skipping to change at line 175 ¶ | skipping to change at line 175 ¶ | |||
registration policies: IETF Review, Specification Required, and | registration policies: IETF Review, Specification Required, and | |||
Private or Experimental Use. | Private or Experimental Use. | |||
Section 7.7 created the "Network Time Security Next Protocols" | Section 7.7 created the "Network Time Security Next Protocols" | |||
registry that similarly partitions the range. | registry that similarly partitions the range. | |||
Section 7.8 created the "Network Time Security Error Codes" and | Section 7.8 created the "Network Time Security Error Codes" and | |||
"Network Time Security Warning Codes" registries. Both registries | "Network Time Security Warning Codes" registries. Both registries | |||
are partitioned the same way. | are partitioned the same way. | |||
3. Registry Updates | 3. NTP Registry Updates | |||
The following general guidelines apply to the NTP registries: | The following general guidelines apply to the NTP registries: | |||
* Each registry reserves a partition for Private or Experimental | * A partition of the "NTP Extension Field Types" registry is | |||
Use. | ||||
* Entries with ASCII fields are now limited to uppercase letters or | ||||
digits; fields starting with 0x58, the uppercase letter "X", are | ||||
reserved for Private or Experimental Use. | reserved for Private or Experimental Use. | |||
* The policy for every registry is now Specification Required, as | * In the "NTP Reference Identifier Codes" and "NTP Kiss-o'-Death | |||
Codes" registries, entries with ASCII fields are now limited to | ||||
uppercase letters or digits. Fields starting with 0x58, the | ||||
uppercase letter "X", are reserved for Private or Experimental | ||||
Use. | ||||
* The policy for each registry is now Specification Required, as | ||||
defined in [RFC8126], Section 4.6. | defined in [RFC8126], Section 4.6. | |||
3.1. Designated Experts | ||||
The IESG is requested to choose three designated experts (DEs), with | The IESG is requested to choose three designated experts (DEs), with | |||
approvals from two being required to implement a change. Guidance | approvals from two being required to implement a change. Guidance | |||
for the experts is given below. | for the experts is given below. | |||
3.1. Guidance to Designated Experts | ||||
The DEs should be familiar with [RFC8126], particularly Section 5. | The DEs should be familiar with [RFC8126], particularly Section 5. | |||
As that reference suggests, the DE should ascertain the existence of | As that reference suggests, the DE should ascertain the existence of | |||
a suitable specification and verify that it is publicly available. | a suitable specification and verify that it is publicly available. | |||
The DE is also expected to check the clarity of purpose and use of | The DE is also expected to check the clarity of purpose and use of | |||
the requested code points. | the requested code points. | |||
In addition, the DE is expected to be familiar with this document, | In addition, the DE is expected to be familiar with this document, | |||
specifically the history documented here. | specifically the history documented here. | |||
4. IANA Considerations | 4. IANA Considerations | |||
End of changes. 6 change blocks. | ||||
11 lines changed or deleted | 13 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. |