RFC 8736: PIM Message Type Space Extension and Reserved Bits
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 8736: PIM Message Type Space Extension and Reserved Bits
Summary
RFC 8736: PIM Message Type Space Extension and Reserved Bits is a Request for Comments[1].
Key Facts
- RFC 8736: PIM Message Type Space Extension and Reserved Bits authored PIM Message Type Space Extension and Reserved Bits — author (P50): Stig Venaas[2].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's instance of is recorded as PIM Message Type Space Extension and Reserved Bits — instance of (P31): Request for Comments[3].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's publisher is recorded as PIM Message Type Space Extension and Reserved Bits — publisher (P123): Internet Engineering Task Force[4].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's based on is recorded as PIM Message Type Space Extension and Reserved Bits — based on (P144): RFC 3973: Protocol Independent Multicast - Dense Mode (PIM-DM): Protocol Specification (Revised)[5].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's based on is recorded as PIM Message Type Space Extension and Reserved Bits — based on (P144): RFC 5015: Bidirectional Protocol Independent Multicast (BIDIR-PIM)[6].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's based on is recorded as PIM Message Type Space Extension and Reserved Bits — based on (P144): RFC 5059: Bootstrap Router (BSR) Mechanism for Protocol Independent Multicast (PIM)[7].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's based on is recorded as PIM Message Type Space Extension and Reserved Bits — based on (P144): RFC 6754: Protocol Independent Multicast Equal-Cost Multipath (ECMP) Redirect[8].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's based on is recorded as PIM Message Type Space Extension and Reserved Bits — based on (P144): RFC 7761: Protocol Independent Multicast - Sparse Mode (PIM-SM): Protocol Specification (Revised)[9].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's based on is recorded as PIM Message Type Space Extension and Reserved Bits — based on (P144): RFC 8364: PIM Flooding Mechanism (PFM) and Source Discovery (SD)[10].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's DOI is recorded as 10.17487/RFC8736[11].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's language of work or name is recorded as PIM Message Type Space Extension and Reserved Bits — language of work or name (P407): English[12].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's publication date is recorded as +2020-02-01T00:00:00Z[13].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's RfC ID is recorded as 8736[14].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's work available at URL is recorded as https://tools.ietf.org/html/rfc8736[15].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's replaces is recorded as PIM Message Type Space Extension and Reserved Bits — replaces (P1365): RFC 6166: A Registry for PIM Message Types[16].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's replaced by is recorded as PIM Message Type Space Extension and Reserved Bits — replaced by (P1366): RFC 9436: PIM Message Type Space Extension and Reserved Bits[17].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's title is recorded as PIM Message Type Space Extension and Reserved Bits[18].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's author name string is recorded as A. Retana[19].
- RFC 8736: PIM Message Type Space Extension and Reserved Bits's DBLP publication ID is recorded as journals/rfc/rfc8736[20].
Body
Designation and Status
RFC 8736: PIM Message Type Space Extension and Reserved Bits's instance of is recorded as PIM Message Type Space Extension and Reserved Bits — instance of (P31): Request for Comments[3].