InterAS MPLS TE Requirements draftzhangmplsinterastereq02'txt

1
Inter-AS MPLS TE Requirementsdraft-zhang-mpls-int
eras-te-req-02.txt
Raymond Zhang, INFONET JP Vasseur, Cisco Kenji
Kumaki, KDDI Paul Mabey, Qwest Nadim Constantine,
INFONET Pierre Merckx, Equant Ting-Wo Chung, Bell
Canada JL Le Roux, France Telecom
2
Update of the Draft -02

• This draft is driven by requirements from SPs
  with matching application scenarios.
• Support and contributions continue to expand
• Revision 00 INFONET, KDDI and Qwest
• Revision 01 Equant
• Revision 02 Bell Canada, France Telecom
• Additionally, we have received very helpful
  comments from Yuichi/NTT and Dave/Nortel which
  are incorporated in -02.

3
Update of the Draft -02

• This draft is NOT about VPN (Layer2 or Layer3),
  but about the requirements for extending MPLS TE
  across AS boundaries
• Application scenarios are used to illustrate the
  requirement of inter-AS MPLS TE, some are in the
  context of L3 VPN services
• This draft is to document requirements that could
  lead to solutions to provide the following
• Resource optimization across AS boundaries
• Resource guarantee along QoS path across multiple
  ASes
• Reliability with Fast local repair upon
  link/SRLG/node failure across inter-AS links.

4
Update of the Draft -02

• The following major areas are updated
• Updated some application scenarios per comments
• Added a new section on re-optimization as one of
  detailed requirements (sec. 5.10)
• Resource condition changes inside any transiting
  AS should trigger re-optimization
• Signaled by the intermediate nodes to the HE
• Ability for HE to trigger better path evaluation
• Others

5
Conclusion

• In IETF 55 (Atlanta), we seem all agree that this
  draft is part of the TEWG charter (meeting
  minutes shown below)
• o) Inter AS requirements
• gt gt see presentation
• gt gt
• gt gt Discussion on if TEWG is right place for
  these types of
• gt gt requirements, show of hands indicated it was
  and there was no
• gt gt objection. Bert confirmed that was his
  understanding of where
• gt gt these would be too. Also, show of hands
  indicated it is about time
• gt gt to take this type of requirements work on.

6
Conclusion

• Whats documented in this draft are concrete
  technical requirements.
• This is the Only reqs draft on this topic today
• Once again, we would like to propose the TE WG to
  adopt this draft as a WG document so as to
• Bring further focus on any additional discussions
  about inter-AS TE requirements
• Begin discussions on solutions
• e.g., http//www.ietf.org/internet-drafts/draft-va
  sseur-inter-as-te-00.txt