-
Notifications
You must be signed in to change notification settings - Fork 12
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
github-actions
committed
Jan 7, 2025
1 parent
422e972
commit 4d3d8bf
Showing
58 changed files
with
2,663 additions
and
75 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,155 @@ | ||
| --- | ||
| schema-version: v1.2.3 | ||
| id: draft-chroboczek-intarea-v4-via-v6-02 | ||
| title: | ||
| - content: IPv4 routes with an IPv6 next hop | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| format: text/plain | ||
| link: | ||
| - content: https://datatracker.ietf.org/doc/html/draft-chroboczek-intarea-v4-via-v6-02 | ||
| type: src | ||
| type: standard | ||
| docid: | ||
| - id: draft-chroboczek-intarea-v4-via-v6-02 | ||
| type: Internet-Draft | ||
| primary: true | ||
| - id: I-D.chroboczek-intarea-v4-via-v6 | ||
| type: IETF | ||
| scope: anchor | ||
| docnumber: I-D.chroboczek-intarea-v4-via-v6 | ||
| date: | ||
| - type: published | ||
| value: '2025-01-06' | ||
| contributor: | ||
| - person: | ||
| name: | ||
| given: | ||
| forename: | ||
| - content: Juliusz | ||
| language: | ||
| - en | ||
| - language: | ||
| - en | ||
| initial: J | ||
| formatted_initials: | ||
| content: J. | ||
| language: | ||
| - en | ||
| surname: | ||
| content: Chroboczek | ||
| language: | ||
| - en | ||
| completename: | ||
| content: Juliusz Chroboczek | ||
| language: | ||
| - en | ||
| affiliation: | ||
| - organization: | ||
| name: | ||
| - content: IRIF, University of Paris | ||
| role: | ||
| - type: author | ||
| - person: | ||
| name: | ||
| given: | ||
| forename: | ||
| - content: Warren | ||
| language: | ||
| - en | ||
| - language: | ||
| - en | ||
| initial: W | ||
| - language: | ||
| - en | ||
| initial: A | ||
| formatted_initials: | ||
| content: W. A. | ||
| language: | ||
| - en | ||
| surname: | ||
| content: Kumari | ||
| language: | ||
| - en | ||
| completename: | ||
| content: Warren "Ace" Kumari | ||
| language: | ||
| - en | ||
| affiliation: | ||
| - organization: | ||
| name: | ||
| - content: Google, LLC | ||
| role: | ||
| - type: author | ||
| - person: | ||
| name: | ||
| given: | ||
| forename: | ||
| - content: Toke | ||
| language: | ||
| - en | ||
| - language: | ||
| - en | ||
| initial: T | ||
| formatted_initials: | ||
| content: T. | ||
| language: | ||
| - en | ||
| surname: | ||
| content: Høiland-Jørgensen | ||
| language: | ||
| - en | ||
| completename: | ||
| content: Toke Høiland-Jørgensen | ||
| language: | ||
| - en | ||
| affiliation: | ||
| - organization: | ||
| name: | ||
| - content: Red Hat | ||
| role: | ||
| - type: author | ||
| version: | ||
| - draft: '02' | ||
| revdate: '2025-01-06' | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| abstract: | ||
| - content: <p>This document proposes "v4-via-v6" routing, a technique that uses IPv6 | ||
| next-hop addresses for routing IPv4 packets, thus making it possible to route | ||
| IPv4 packets across a network where routers have not been assigned IPv4 addresses. | ||
| The document both describes the technique, as well as discussing its operational | ||
| implications.</p> | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| format: text/html | ||
| relation: | ||
| - type: updates | ||
| bibitem: | ||
| id: draft-chroboczek-intarea-v4-via-v6-01 | ||
| docid: | ||
| - id: draft-chroboczek-intarea-v4-via-v6-01 | ||
| type: Internet-Draft | ||
| primary: true | ||
| formattedref: | ||
| content: draft-chroboczek-intarea-v4-via-v6-01 | ||
| format: text/plain | ||
| series: | ||
| - type: main | ||
| title: | ||
| content: Internet-Draft | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| format: text/plain | ||
| number: draft-chroboczek-intarea-v4-via-v6-02 | ||
| doctype: internet-draft | ||
| ext: | ||
| schema-version: v1.0.1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,136 @@ | ||
| --- | ||
| schema-version: v1.2.3 | ||
| id: draft-ietf-dnsop-rfc8624-bis-03 | ||
| title: | ||
| - content: DNSSEC Cryptographic Algorithm Recommendation Update Process | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| format: text/plain | ||
| link: | ||
| - content: https://datatracker.ietf.org/doc/html/draft-ietf-dnsop-rfc8624-bis-03 | ||
| type: src | ||
| type: standard | ||
| docid: | ||
| - id: draft-ietf-dnsop-rfc8624-bis-03 | ||
| type: Internet-Draft | ||
| primary: true | ||
| - id: I-D.ietf-dnsop-rfc8624-bis | ||
| type: IETF | ||
| scope: anchor | ||
| docnumber: I-D.ietf-dnsop-rfc8624-bis | ||
| date: | ||
| - type: published | ||
| value: '2025-01-06' | ||
| contributor: | ||
| - person: | ||
| name: | ||
| given: | ||
| forename: | ||
| - content: Wes | ||
| language: | ||
| - en | ||
| - language: | ||
| - en | ||
| initial: W | ||
| formatted_initials: | ||
| content: W. | ||
| language: | ||
| - en | ||
| surname: | ||
| content: Hardaker | ||
| language: | ||
| - en | ||
| completename: | ||
| content: Wes Hardaker | ||
| language: | ||
| - en | ||
| affiliation: | ||
| - organization: | ||
| name: | ||
| - content: USC/ISI | ||
| role: | ||
| - type: author | ||
| - person: | ||
| name: | ||
| given: | ||
| forename: | ||
| - content: Warren | ||
| language: | ||
| - en | ||
| - language: | ||
| - en | ||
| initial: W | ||
| - language: | ||
| - en | ||
| initial: A | ||
| formatted_initials: | ||
| content: W. A. | ||
| language: | ||
| - en | ||
| surname: | ||
| content: Kumari | ||
| language: | ||
| - en | ||
| completename: | ||
| content: Warren "Ace" Kumari | ||
| language: | ||
| - en | ||
| affiliation: | ||
| - organization: | ||
| name: | ||
| - content: Google | ||
| role: | ||
| - type: author | ||
| version: | ||
| - draft: '03' | ||
| revdate: '2025-01-06' | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| abstract: | ||
| - content: "<p><EDITOR NOTE: This document does not change the status (MUST, MAY, | ||
| RECOMMENDED, etc) of any of the algorithms listed in [RFC8624]; that is the work | ||
| of future documents. Instead, this document moves the canonical list of algorithms | ||
| from [RFC8624] to an IANA registry. This is done for two reasons: 1) to allow | ||
| the list to be updated more easily, and, much more importantly, 2) to allow the | ||
| list to be more easily referenced.> The DNSSEC protocol makes use of various | ||
| cryptographic algorithms to provide authentication of DNS data and proof of non-existence. | ||
| To ensure interoperability between DNS resolvers and DNS authoritative servers, | ||
| it is necessary to specify both a set of algorithm implementation requirements | ||
| and usage guidelines to ensure that there is at least one algorithm that all implementations | ||
| support. This document updates RFC8624 by moving the canonical source of algorithm | ||
| implementation requirements and usage guidance for DNSSEC from [RFC8624] to an | ||
| IANA registry. Future extensions to this registry can be made under new, incremental | ||
| update RFCs.</p>" | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| format: text/html | ||
| relation: | ||
| - type: updates | ||
| bibitem: | ||
| id: draft-ietf-dnsop-rfc8624-bis-02 | ||
| docid: | ||
| - id: draft-ietf-dnsop-rfc8624-bis-02 | ||
| type: Internet-Draft | ||
| primary: true | ||
| formattedref: | ||
| content: draft-ietf-dnsop-rfc8624-bis-02 | ||
| format: text/plain | ||
| series: | ||
| - type: main | ||
| title: | ||
| content: Internet-Draft | ||
| language: | ||
| - en | ||
| script: | ||
| - Latn | ||
| format: text/plain | ||
| number: draft-ietf-dnsop-rfc8624-bis-03 | ||
| doctype: internet-draft | ||
| ext: | ||
| schema-version: v1.0.1 |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.