RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)
0 sources
RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)
Summary
RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) is a Request for Comments[1].
Key Facts
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) authored State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) — author (P50): Bryan Ford[2].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) authored State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) — author (P50): Pyda Srisuresh[3].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) authored State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) — author (P50): Dan Kegel[4].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s instance of is recorded as State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) — instance of (P31): Request for Comments[5].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s publisher is recorded as State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) — publisher (P123): Internet Engineering Task Force[6].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s DOI is recorded as 10.17487/RFC5128[7].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s language of work or name is recorded as State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) — language of work or name (P407): English[8].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s publication date is recorded as +2008-03-01T00:00:00Z[9].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s RfC ID is recorded as 5128[10].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s work available at URL is recorded as https://tools.ietf.org/html/rfc5128[11].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s work available at URL is recorded as https://tools.ietf.org/rfc/rfc5128.txt[12].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc5128.txt[13].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc5128.txt.pdf[14].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s number of pages is recorded as {'unit': '1', 'amount': '+32'}[15].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s title is recorded as State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)[16].
- RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s DBLP publication ID is recorded as journals/rfc/rfc5128[17].
Body
Designation and Status
RFC 5128: State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs)'s instance of is recorded as State of Peer-to-Peer (P2P) Communication across Network Address Translators (NATs) — instance of (P31): Request for Comments[5].