RFC 1966: BGP Route Reflection An alternative to full mesh IBGP
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 1966: BGP Route Reflection An alternative to full mesh IBGP
Summary
RFC 1966: BGP Route Reflection An alternative to full mesh IBGP is a Request for Comments[1].
Key Facts
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's instance of is recorded as BGP Route Reflection An alternative to full mesh IBGP — instance of (P31): Request for Comments[2].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's publisher is recorded as BGP Route Reflection An alternative to full mesh IBGP — publisher (P123): Internet Engineering Task Force[3].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's DOI is recorded as 10.17487/RFC1966[4].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's language of work or name is recorded as BGP Route Reflection An alternative to full mesh IBGP — language of work or name (P407): English[5].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's publication date is recorded as +1996-06-01T00:00:00Z[6].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's RfC ID is recorded as 1966[7].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's main subject is recorded as BGP Route Reflection An alternative to full mesh IBGP — main subject (P921): Border Gateway Protocol[8].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's work available at URL is recorded as https://tools.ietf.org/html/rfc1966[9].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's work available at URL is recorded as https://tools.ietf.org/rfc/rfc1966.txt[10].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc1966.txt[11].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc1966.txt.pdf[12].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's number of pages is recorded as {'unit': '1', 'amount': '+7'}[13].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's replaced by is recorded as BGP Route Reflection An alternative to full mesh IBGP — replaced by (P1366): RFC 4456: BGP Route Reflection: An Alternative to Full Mesh Internal BGP (IBGP)[14].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's title is recorded as BGP Route Reflection An alternative to full mesh IBGP[15].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's author name string is recorded as T. Bates[16].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's author name string is recorded as R. Chandra[17].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's amended by is recorded as BGP Route Reflection An alternative to full mesh IBGP — amended by (P2567): RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP[18].
- RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's DBLP publication ID is recorded as journals/rfc/rfc1966[19].
Body
Designation and Status
RFC 1966: BGP Route Reflection An alternative to full mesh IBGP's instance of is recorded as BGP Route Reflection An alternative to full mesh IBGP — instance of (P31): Request for Comments[2].