draft-ietf-idr-ls-distribution-12.txt   draft-ietf-idr-ls-distribution-13.txt 
Inter-Domain Routing H. Gredler, Ed. Inter-Domain Routing H. Gredler, Ed.
Internet-Draft Private Contributor Internet-Draft Private Contributor
Intended status: Standards Track J. Medved Intended status: Standards Track J. Medved
Expires: April 6, 2016 S. Previdi Expires: April 18, 2016 S. Previdi
Cisco Systems, Inc. Cisco Systems, Inc.
A. Farrel A. Farrel
Juniper Networks, Inc. Juniper Networks, Inc.
S. Ray S. Ray
October 4, 2015 October 16, 2015
North-Bound Distribution of Link-State and TE Information using BGP North-Bound Distribution of Link-State and TE Information using BGP
draft-ietf-idr-ls-distribution-12 draft-ietf-idr-ls-distribution-13
Abstract Abstract
In a number of environments, a component external to a network is In a number of environments, a component external to a network is
called upon to perform computations based on the network topology and called upon to perform computations based on the network topology and
current state of the connections within the network, including current state of the connections within the network, including
traffic engineering information. This is information typically traffic engineering information. This is information typically
distributed by IGP routing protocols within the network. distributed by IGP routing protocols within the network.
This document describes a mechanism by which links state and traffic This document describes a mechanism by which links state and traffic
skipping to change at page 2, line 10 skipping to change at page 2, line 10
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet- working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/. Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress." material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 6, 2016. This Internet-Draft will expire on April 18, 2016.
Copyright Notice Copyright Notice
Copyright (c) 2015 IETF Trust and the persons identified as the Copyright (c) 2015 IETF Trust and the persons identified as the
document authors. All rights reserved. document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of (http://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents publication of this document. Please review these documents
skipping to change at page 3, line 32 skipping to change at page 3, line 32
8. Security Considerations . . . . . . . . . . . . . . . . . . . 42 8. Security Considerations . . . . . . . . . . . . . . . . . . . 42
9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 43 9. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 43
10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 43 10. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 43
11. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 11. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
11.1. Normative References . . . . . . . . . . . . . . . . . . 43 11.1. Normative References . . . . . . . . . . . . . . . . . . 43
11.2. Informative References . . . . . . . . . . . . . . . . . 45 11.2. Informative References . . . . . . . . . . . . . . . . . 45
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47
1. Introduction 1. Introduction
The contents of a Link State Database (LSDB) or a Traffic Engineering The contents of a Link State Database (LSDB) or of an IGP's Traffic
Database (TED) has the scope of an IGP area. Some applications, such Engineering Database (TED) describe only the links and nodes within
as end-to-end Traffic Engineering (TE), would benefit from visibility an IGP area. Some applications, such as end-to-end Traffic
outside one area or Autonomous System (AS) in order to make better Engineering (TE), would benefit from visibility outside one area or
decisions. Autonomous System (AS) in order to make better decisions.
The IETF has defined the Path Computation Element (PCE) [RFC4655] as The IETF has defined the Path Computation Element (PCE) [RFC4655] as
a mechanism for achieving the computation of end-to-end TE paths that a mechanism for achieving the computation of end-to-end TE paths that
cross the visibility of more than one TED or which require CPU- cross the visibility of more than one TED or which require CPU-
intensive or coordinated computations. The IETF has also defined the intensive or coordinated computations. The IETF has also defined the
ALTO Server [RFC5693] as an entity that generates an abstracted ALTO Server [RFC5693] as an entity that generates an abstracted
network topology and provides it to network-aware applications. network topology and provides it to network-aware applications.
Both a PCE and an ALTO Server need to gather information about the Both a PCE and an ALTO Server need to gather information about the
topologies and capabilities of the network in order to be able to topologies and capabilities of the network in order to be able to
skipping to change at page 36, line 34 skipping to change at page 36, line 34
5. IANA Considerations 5. IANA Considerations
This document is the reference for Address Family Number 16388, 'BGP- This document is the reference for Address Family Number 16388, 'BGP-
LS'. LS'.
This document requests code point 71 from the registry of Subsequent This document requests code point 71 from the registry of Subsequent
Address Family Numbers named 'BGP-LS'. Address Family Numbers named 'BGP-LS'.
This document requests a code point from the registry of Subsequent This document requests a code point from the registry of Subsequent
Address Family Numbers named 'BGP-LS-VPN'. The SAFI assignment does Address Family Numbers named 'BGP-LS-VPN'. The SAFI assignment does
NOT need to be out of the range 1-63 and MAY come out of the "First not need to be out of the range 1-63 and may come out of the "First
Come First Served" range 128-240. Come First Served" range 128-240.
This document requests a code point from the BGP Path Attributes This document requests a code point from the BGP Path Attributes
registry. As per early allocation procedure this is Path Attribute registry. As per early allocation procedure this is Path Attribute
29. 29.
All the following Registries are BGP-LS specific and shall be All the following Registries are BGP-LS specific and shall be
accessible under the following URL: "http://www.iana.org/assignments/ accessible under the following URL: "http://www.iana.org/assignments/
bgp-ls-parameters" Title "Border Gateway Protocol - Link State (BGP- bgp-ls-parameters" Title "Border Gateway Protocol - Link State (BGP-
LS) Parameters" LS) Parameters"
skipping to change at page 43, line 17 skipping to change at page 43, line 17
We would like to thank Robert Varga for the significant contribution We would like to thank Robert Varga for the significant contribution
he gave to this document. he gave to this document.
10. Acknowledgements 10. Acknowledgements
We would like to thank Nischal Sheth, Alia Atlas, David Ward, Derek We would like to thank Nischal Sheth, Alia Atlas, David Ward, Derek
Yeung, Murtuza Lightwala, John Scudder, Kaliraj Vairavakkalai, Les Yeung, Murtuza Lightwala, John Scudder, Kaliraj Vairavakkalai, Les
Ginsberg, Liem Nguyen, Manish Bhardwaj, Matt Miller, Mike Shand, Ginsberg, Liem Nguyen, Manish Bhardwaj, Matt Miller, Mike Shand,
Peter Psenak, Rex Fernando, Richard Woundy, Steven Luong, Tamas Peter Psenak, Rex Fernando, Richard Woundy, Steven Luong, Tamas
Mondal, Waqas Alam, Vipin Kumar, Naiming Shen, Carlos Pignataro, Mondal, Waqas Alam, Vipin Kumar, Naiming Shen, Carlos Pignataro,
Balaji Rajagopalan, Yakov Rekhter, and Alvaro Retana for their Balaji Rajagopalan, Yakov Rekhter, Alvaro Retana, Barry Leiba, and
comments. Ben Campbell for their comments.
11. References 11. References
11.1. Normative References 11.1. Normative References
[RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and [RFC1195] Callon, R., "Use of OSI IS-IS for routing in TCP/IP and
dual environments", RFC 1195, DOI 10.17487/RFC1195, dual environments", RFC 1195, DOI 10.17487/RFC1195,
December 1990, <http://www.rfc-editor.org/info/rfc1195>. December 1990, <http://www.rfc-editor.org/info/rfc1195>.
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
 End of changes. 7 change blocks. 
12 lines changed or deleted 12 lines changed or added

This html diff was produced by rfcdiff 1.42. The latest version is available from http://tools.ietf.org/tools/rfcdiff/