RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
0 sources
RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)
Summary
RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified) is a Request for Comments[1].
Key Facts
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified) authored Network 10 Considered Harmful (Some Practices Shouldn't be Codified) — author (P50): Steve Crocker[2].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified) authored Network 10 Considered Harmful (Some Practices Shouldn't be Codified) — author (P50): Eliot Lear[3].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s instance of is recorded as Network 10 Considered Harmful (Some Practices Shouldn't be Codified) — instance of (P31): Request for Comments[4].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s publisher is recorded as Network 10 Considered Harmful (Some Practices Shouldn't be Codified) — publisher (P123): Internet Engineering Task Force[5].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s DOI is recorded as 10.17487/RFC1627[6].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s language of work or name is recorded as Network 10 Considered Harmful (Some Practices Shouldn't be Codified) — language of work or name (P407): English[7].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s publication date is recorded as +1994-07-01T00:00:00Z[8].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s RfC ID is recorded as 1627[9].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s work available at URL is recorded as https://tools.ietf.org/html/rfc1627[10].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc1627.txt[11].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc1627.txt[12].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc1627.txt.pdf[13].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s number of pages is recorded as {'unit': '1', 'amount': '+8'}[14].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s replaced by is recorded as Network 10 Considered Harmful (Some Practices Shouldn't be Codified) — replaced by (P1366): RFC 1918: Address Allocation for Private Internets[15].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s title is recorded as Network 10 Considered Harmful (Some Practices Shouldn't be Codified)[16].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s author name string is recorded as E. Fair[17].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s author name string is recorded as T. Kessler[18].
- RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s DBLP publication ID is recorded as journals/rfc/rfc1627[19].
Body
Designation and Status
RFC 1627: Network 10 Considered Harmful (Some Practices Shouldn't be Codified)'s instance of is recorded as Network 10 Considered Harmful (Some Practices Shouldn't be Codified) — instance of (P31): Request for Comments[4].