RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC
0 sources
RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC
Summary
RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC is a Request for Comments[1].
Key Facts
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC authored Cryptographic Algorithm Identifier Allocation for DNSSEC — author (P50): Paul Hoffman[2].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's instance of is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — instance of (P31): Request for Comments[3].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's publisher is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — publisher (P123): Internet Engineering Task Force[4].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's based on is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — based on (P144): RFC 4033: DNS Security Introduction and Requirements[5].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's based on is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — based on (P144): RFC 4034: Resource Records for the DNS Security Extensions[6].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's based on is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — based on (P144): RFC 4035: Protocol Modifications for the DNS Security Extensions[7].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's DOI is recorded as 10.17487/RFC6014[8].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's language of work or name is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — language of work or name (P407): English[9].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's publication date is recorded as +2010-11-01T00:00:00Z[10].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's RfC ID is recorded as 6014[11].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's work available at URL is recorded as https://tools.ietf.org/html/rfc6014[12].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6014.txt[13].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6014.txt[14].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6014.txt.pdf[15].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's number of pages is recorded as {'unit': '1', 'amount': '+6'}[16].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's title is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC[17].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's amended by is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — amended by (P2567): RFC 9157: Revised IANA Considerations for DNSSEC[18].
- RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's DBLP publication ID is recorded as journals/rfc/rfc6014[19].
Body
Designation and Status
RFC 6014: Cryptographic Algorithm Identifier Allocation for DNSSEC's instance of is recorded as Cryptographic Algorithm Identifier Allocation for DNSSEC — instance of (P31): Request for Comments[3].