RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
0 sources
RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery
Summary
RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery is a Request for Comments[1].
Key Facts
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery authored Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery — author (P50): Fernando Gont[2].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's instance of is recorded as Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery — instance of (P31): Request for Comments[3].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's publisher is recorded as Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery — publisher (P123): Internet Engineering Task Force[4].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's based on is recorded as Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery — based on (P144): RFC 3971: SEcure Neighbor Discovery (SEND)[5].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's based on is recorded as Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery — based on (P144): RFC 4861: Neighbor Discovery for IP version 6 (IPv6)[6].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's DOI is recorded as 10.17487/RFC6980[7].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's language of work or name is recorded as Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery — language of work or name (P407): English[8].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's publication date is recorded as +2013-08-01T00:00:00Z[9].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's RfC ID is recorded as 6980[10].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's work available at URL is recorded as https://tools.ietf.org/html/rfc6980[11].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's work available at URL is recorded as https://tools.ietf.org/rfc/rfc6980.txt[12].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc6980.txt[13].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc6980.txt.pdf[14].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's number of pages is recorded as {'unit': '1', 'amount': '+10'}[15].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's title is recorded as Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery[16].
- RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's DBLP publication ID is recorded as journals/rfc/rfc6980[17].
Body
Designation and Status
RFC 6980: Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery's instance of is recorded as Security Implications of IPv6 Fragmentation with IPv6 Neighbor Discovery — instance of (P31): Request for Comments[3].