draft-ietf-tewg-interas-mpls-te-req-07.txt   draft-ietf-tewg-interas-mpls-te-req-08.txt 
IETF Internet Draft Raymond Zhang, Editor IETF Internet Draft Raymond Zhang, Editor
Internet Engineering Task Force Infonet Services Corporation Internet Engineering Task Force Infonet Services Corporation
draft-ietf-tewg-interas-mpls-te-req-07.txt JP Vasseur, Co-Editor draft-ietf-tewg-interas-mpls-te-req-08.txt JP Vasseur, Co-Editor
Expires: Dec. 2004 CISCO Systems,Inc Expires: Feb. 2005 CISCO Systems,Inc
June 2004 August 2004
MPLS Inter-AS Traffic Engineering requirements MPLS Inter-AS Traffic Engineering requirements
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with This document is an Internet-Draft and is in full conformance with
all provisions of Section 10 of RFC2026. Internet-Drafts are working all provisions of Section 10 of RFC2026. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, documents of the Internet Engineering Task Force (IETF), its areas,
and its working groups. Note that other groups may also distribute and its working groups. Note that other groups may also distribute
working documents as Internet-Drafts. working documents as Internet-Drafts.
skipping to change at page 1, line 39 skipping to change at page 2, line 5
Abstract Abstract
This document discusses requirements for the support of inter-AS This document discusses requirements for the support of inter-AS
MPLS Traffic Engineering (MPLS TE). Its main objective is to MPLS Traffic Engineering (MPLS TE). Its main objective is to
present a set of requirements which would result in general present a set of requirements which would result in general
guidelines for the definition, selection and guidelines for the definition, selection and
specification development for any technical solution(s) meeting specification development for any technical solution(s) meeting
these requirements. these requirements.
Summary for Sub-IP related Internet Drafts
RELATED DOCUMENTS:
None
WHERE DOES IT FIT IN THE PICTURE OF THE SUB-IP WORK
TEWG
WHY IS IT TARGETED AT THIS WG(s)
It is stated in the charter that documenting SP requirements in this
area is one of the work items to be undertaken by TEWG.
JUSTIFICATION
The TEWG charter further states that "The working group may also
consider the problems of traffic engineering across autonomous
systems boundaries."
MPLS Inter-AS TE requirements June 2004 MPLS Inter-AS TE requirements June 2004
This draft discusses the requirements for a traffic engineering
mechanism across autonomous systems boundaries that would also be
interoperable with current intra-AS traffic engineering mechanisms.
Conventions used in this document Conventions used in this document
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC-2119. this document are to be interpreted as described in [RFC-2119].
Table of Contents Table of Contents
1. Introduction.......................................................3 1. Introduction.......................................................3
2. Contributing Authors...............................................4 2. Contributing Authors...............................................4
3. Definitions and Requirements Statement.............................5 3. Definitions and Requirements Statement.............................5
3.1. Definitions......................................................5 3.1. Definitions......................................................5
3.2. Objectives and Requirements of Inter-AS Traffic Engineering......6 3.2. Objectives and Requirements of Inter-AS Traffic Engineering......6
3.2.1. Inter-AS Bandwidth Guarantees..................................6 3.2.1. Inter-AS Bandwidth Guarantees..................................6
3.2.2. Inter-AS Resource Optimization.................................7 3.2.2. Inter-AS Resource Optimization.................................7
skipping to change at page 23, line 14 skipping to change at page 23, line 15
MPLS Inter-AS TE requirements June 2004 MPLS Inter-AS TE requirements June 2004
9. Normative References 9. Normative References
[TE-REQ], Awduche et. al., "Requirements for Traffic Engineering [TE-REQ], Awduche et. al., "Requirements for Traffic Engineering
over MPLS", RFC2702, September 1999. over MPLS", RFC2702, September 1999.
[TE-RSVP], Awduche et. al., "RSVP-TE: Extensions to RSVP for LSP [TE-RSVP], Awduche et. al., "RSVP-TE: Extensions to RSVP for LSP
Tunnels", RFC 3209, December 2001 Tunnels", RFC 3209, December 2001
[RFC-2119], S. Bradner, "Key words for use in RFCs to Indicate
Requirement Levels", RFC 2119, March 1997
10. Informative References 10. Informative References
[MPLS-ARCH], Rosen, et. al., "Multiprotocol Label Switching [MPLS-ARCH], Rosen, et. al., "Multiprotocol Label Switching
Architecture", RFC 3031, January 2001 Architecture", RFC 3031, January 2001
[BGP-MPLSVPN], Rosen, et. al., "BGP/MPLSVPN", draft-ietf-l3vpn [BGP-MPLSVPN], Rosen, et. al., "BGP/MPLSVPN", draft-ietf-l3vpn
-rfc2547bis-01.txt, September 2003 (work in progress). -rfc2547bis-01.txt, September 2003 (work in progress).
[DIFF_ARCH], Blake, et. al., "An Architecture for Differentiated [DIFF_ARCH], Blake, et. al., "An Architecture for Differentiated
Services", RFC 2475, December 1998. Services", RFC 2475, December 1998.
 End of changes. 

This html diff was produced by rfcdiff 1.25, available from http://www.levkowetz.com/ietf/tools/rfcdiff/