| rfc8618v5.txt | rfc8618-SD-5.txt | |||
|---|---|---|---|---|
| skipping to change at page 47, line 41 ¶ | skipping to change at page 47, line 41 ¶ | |||
| IANA has created a registry "C-DNS Transports" of C-DNS transport | IANA has created a registry "C-DNS Transports" of C-DNS transport | |||
| type identifiers. The primary purpose of this registry is to provide | type identifiers. The primary purpose of this registry is to provide | |||
| unique identifiers for all transports used for DNS Queries. | unique identifiers for all transports used for DNS Queries. | |||
| The following note is included in this registry: "In version 1.0 of | The following note is included in this registry: "In version 1.0 of | |||
| C-DNS [RFC8618], there is a field to identify the type of DNS | C-DNS [RFC8618], there is a field to identify the type of DNS | |||
| transport. This field is 4 bits in size." | transport. This field is 4 bits in size." | |||
| The initial contents of the registry are as follows. See | The initial contents of the registry are as follows. See | |||
| Sections 7.5.3.2 and 7.5.3.5 of this document: | Sections 7.5.3.2 and 7.5.3.5 and 7.7 of this document: | |||
| +------------+------------+-----------+ | +------------+------------------------+-----------+ | |||
| | Identifier | Name | Reference | | | Identifier | Name | Reference | | |||
| +------------+------------+-----------+ | +------------+------------------------+-----------+ | |||
| | 0 | UDP | RFC 8618 | | | 0 | UDP | RFC 8618 | | |||
| | 1 | TCP | RFC 8618 | | | 1 | TCP | RFC 8618 | | |||
| | 2 | TLS | RFC 8618 | | | 2 | TLS | RFC 8618 | | |||
| | 3 | DTLS | RFC 8618 | | | 3 | DTLS | RFC 8618 | | |||
| | 4 | HTTPS | RFC 8618 | | | 4 | HTTPS | RFC 8618 | | |||
| | 5-15 | Unassigned | | | | 5-14 | Unassigned | | | |||
| +------------+------------+-----------+ | | 15 | Non-standard transport | RFC 8618 | | |||
| +------------+------------------------+-----------+ | ||||
| Expert reviewers should take the following point into consideration: | Expert reviewers should take the following point into consideration: | |||
| Is the requested DNS transport described by a Standards Track RFC? | Is the requested DNS transport described by a Standards Track RFC? | |||
| 12.2. Data Storage Flags | 12.2. Data Storage Flags | |||
| IANA has created a registry "C-DNS Storage Flags" of C-DNS data | IANA has created a registry "C-DNS Storage Flags" of C-DNS data | |||
| storage flags. The primary purpose of this registry is to provide | storage flags. The primary purpose of this registry is to provide | |||
| indicators giving hints on processing of the data stored. | indicators giving hints on processing of the data stored. | |||
| End of changes. 2 change blocks. | ||||
| 11 lines changed or deleted | 12 lines changed or added | |||
This html diff was produced by rfcdiff 1.45. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||