RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering

Summary

RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering is a Request for Comments^[1].

Key Facts

• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering authored Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering — author (P50): Wai Sum Lai^[2].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering authored Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering — author (P50): François Le Faucheur^[3].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's instance of is recorded as Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering — instance of (P31): Request for Comments^[4].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's publisher is recorded as Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering — publisher (P123): Internet Engineering Task Force^[5].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's DOI is recorded as 10.17487/RFC3564^[6].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's language of work or name is recorded as Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering — language of work or name (P407): English^[7].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's publication date is recorded as +2003-07-01T00:00:00Z^[8].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's RfC ID is recorded as 3564^[9].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's work available at URL is recorded as https://tools.ietf.org/html/rfc3564^[10].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's work available at URL is recorded as https://tools.ietf.org/rfc/rfc3564.txt^[11].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's work available at URL is recorded as https://www.rfc-editor.org/rfc/rfc3564.txt^[12].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's work available at URL is recorded as https://www.rfc-editor.org/pdfrfc/rfc3564.txt.pdf^[13].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's number of pages is recorded as {'unit': '1', 'amount': '+22'}^[14].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's title is recorded as Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering^[15].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's amended by is recorded as Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering — amended by (P2567): RFC 5462: Multiprotocol Label Switching (MPLS) Label Stack Entry: "EXP" Field Renamed to "Traffic Class" Field^[16].
• RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's DBLP publication ID is recorded as journals/rfc/rfc3564^[17].

Body

Designation and Status

RFC 3564: Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering's instance of is recorded as Requirements for Support of Differentiated Services-aware MPLS Traffic Engineering — instance of (P31): Request for Comments^[4].