RFC 1670: Input to IPng Engineering Considerations
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 1670: Input to IPng Engineering Considerations
Summary
RFC 1670: Input to IPng Engineering Considerations is a Request for Comments[1].
Key Facts
- RFC 1670: Input to IPng Engineering Considerations's instance of is recorded as Input to IPng Engineering Considerations — instance of (P31): Request for Comments[2].
- RFC 1670: Input to IPng Engineering Considerations's publisher is recorded as Input to IPng Engineering Considerations — publisher (P123): Internet Engineering Task Force[3].
- RFC 1670: Input to IPng Engineering Considerations's DOI is recorded as 10.17487/RFC1670[4].
- RFC 1670: Input to IPng Engineering Considerations's language of work or name is recorded as Input to IPng Engineering Considerations — language of work or name (P407): English[5].
- RFC 1670: Input to IPng Engineering Considerations's publication date is recorded as +1994-08-01T00:00:00Z[6].
- RFC 1670: Input to IPng Engineering Considerations's RfC ID is recorded as 1670[7].
- RFC 1670: Input to IPng Engineering Considerations's main subject is recorded as Input to IPng Engineering Considerations — main subject (P921): IPv6[8].
- RFC 1670: Input to IPng Engineering Considerations's work available at URL is recorded as https://tools.ietf.org/html/rfc1670[9].
- RFC 1670: Input to IPng Engineering Considerations's work available at URL is recorded as https://tools.ietf.org/rfc/rfc1670.txt[10].
- RFC 1670: Input to IPng Engineering Considerations's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc1670.txt[11].
- RFC 1670: Input to IPng Engineering Considerations's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc1670.txt.pdf[12].
- RFC 1670: Input to IPng Engineering Considerations's number of pages is recorded as {'unit': '1', 'amount': '+3'}[13].
- RFC 1670: Input to IPng Engineering Considerations's title is recorded as Input to IPng Engineering Considerations[14].
- RFC 1670: Input to IPng Engineering Considerations's author name string is recorded as D. Heagerty[15].
- RFC 1670: Input to IPng Engineering Considerations's DBLP publication ID is recorded as journals/rfc/rfc1670[16].
Body
Designation and Status
RFC 1670: Input to IPng Engineering Considerations's instance of is recorded as Input to IPng Engineering Considerations — instance of (P31): Request for Comments[2].