RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP
0 sources
RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP
Summary
RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP is a Request for Comments[1].
Key Facts
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP authored BGP Route Reflection - An Alternative to Full Mesh IBGP — author (P50): Enke Chen[2].
- RFC 2796: 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[3].
- RFC 2796: 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[4].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's based on is recorded as BGP Route Reflection - An Alternative to Full Mesh IBGP — based on (P144): RFC 1966: BGP Route Reflection An alternative to full mesh IBGP[5].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's DOI is recorded as 10.17487/RFC2796[6].
- RFC 2796: 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[7].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's publication date is recorded as +2000-04-01T00:00:00Z[8].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's RfC ID is recorded as 2796[9].
- RFC 2796: 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[10].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's work available at URL is recorded as https://tools.ietf.org/html/rfc2796[11].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's work available at URL is recorded as https://tools.ietf.org/rfc/rfc2796.txt[12].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc2796.txt[13].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc2796.txt.pdf[14].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's number of pages is recorded as {'unit': '1', 'amount': '+11'}[15].
- RFC 2796: 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)[16].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's title is recorded as BGP Route Reflection - An Alternative to Full Mesh IBGP[17].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's author name string is recorded as T. Bates[18].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's author name string is recorded as R. Chandra[19].
- RFC 2796: BGP Route Reflection - An Alternative to Full Mesh IBGP's DBLP publication ID is recorded as journals/rfc/rfc2796[20].
Body
Designation and Status
RFC 2796: 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[3].