RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2
request for comments publication
Press Enter · cited answer in seconds
0 sources
RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2
Summary
RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2 is a Request for Comments[1].
Key Facts
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2 authored Traffic Engineering (TE) Extensions to OSPF Version 2 — author (P50): Kireeti Kompella[2].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's instance of is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2 — instance of (P31): Request for Comments[3].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's publisher is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2 — publisher (P123): Internet Engineering Task Force[4].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's based on is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2 — based on (P144): RFC 2370: The OSPF Opaque LSA Option[5].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's DOI is recorded as 10.17487/RFC3630[6].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's language of work or name is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2 — language of work or name (P407): English[7].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's publication date is recorded as +2003-09-01T00:00:00Z[8].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's RfC ID is recorded as 3630[9].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's work available at URL is recorded as https://tools.ietf.org/html/rfc3630[10].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3630.txt[11].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3630.txt[12].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3630.txt.pdf[13].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's number of pages is recorded as {'unit': '1', 'amount': '+14'}[14].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's title is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2[15].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's author name string is recorded as D. Katz[16].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's author name string is recorded as D. Yeung[17].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's amended by is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2 — amended by (P2567): RFC 4203: OSPF Extensions in Support of Generalized Multi-Protocol Label Switching (GMPLS)[18].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's amended by is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2 — amended by (P2567): RFC 5786: Advertising a Router's Local Addresses in OSPF Traffic Engineering (TE) Extensions[19].
- RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's DBLP publication ID is recorded as journals/rfc/rfc3630[20].
Body
Designation and Status
RFC 3630: Traffic Engineering (TE) Extensions to OSPF Version 2's instance of is recorded as Traffic Engineering (TE) Extensions to OSPF Version 2 — instance of (P31): Request for Comments[3].