draft-ietf-idr-ls-distribution-07.txt   draft-ietf-idr-ls-distribution-08.txt 
Inter-Domain Routing H. Gredler Inter-Domain Routing H. Gredler
Internet-Draft Juniper Networks, Inc. Internet-Draft Juniper Networks, Inc.
Intended status: Standards Track J. Medved Intended status: Standards Track J. Medved
Expires: May 19, 2015 S. Previdi Expires: July 24, 2015 S. Previdi
Cisco Systems, Inc. Cisco Systems, Inc.
A. Farrel A. Farrel
Juniper Networks, Inc. Juniper Networks, Inc.
S. Ray S. Ray
Cisco Systems, Inc. Cisco Systems, Inc.
November 15, 2014 January 20, 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-07 draft-ietf-idr-ls-distribution-08
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 12 skipping to change at page 2, line 12
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 May 19, 2015. This Internet-Draft will expire on July 24, 2015.
Copyright Notice Copyright Notice
Copyright (c) 2014 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
carefully, as they describe your rights and restrictions with respect carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as the Trust Legal Provisions and are provided without warranty as
skipping to change at page 12, line 5 skipping to change at page 12, line 5
Both OSPF and IS-IS MAY run multiple routing protocol instances over Both OSPF and IS-IS MAY run multiple routing protocol instances over
the same link. See [RFC6822] and [RFC6549]. These instances define the same link. See [RFC6822] and [RFC6549]. These instances define
independent "routing universes". The 64-Bit 'Identifier' field is independent "routing universes". The 64-Bit 'Identifier' field is
used to identify the "routing universe" where the NLRI belongs. The used to identify the "routing universe" where the NLRI belongs. The
NLRIs representing Link-state objects (nodes, links or prefixes) from NLRIs representing Link-state objects (nodes, links or prefixes) from
the same routing universe MUST have the same 'Identifier' value; the same routing universe MUST have the same 'Identifier' value;
NLRIs with different 'Identifier' values MUST be considered to be NLRIs with different 'Identifier' values MUST be considered to be
from different routing universes. Table Table 3 lists the from different routing universes. Table Table 3 lists the
'Identifier' values that are defined as well-known in this draft. 'Identifier' values that are defined as well-known in this draft.
+------------+---------------------+ +------------+----------------------------------+
| Identifier | Routing Universe | | Identifier | Routing Universe |
+------------+---------------------+ +------------+----------------------------------+
| 0 | L3 packet topology | | 0 | Default Layer 3 Routing topology |
| 1 | L1 optical topology | | 1-31 | Reserved for future use |
+------------+---------------------+ +------------+----------------------------------+
Table 3: Well-known Instance Identifiers Table 3: Well-known Instance Identifiers
If a given Protocol does not support multiple routing universes then If a given Protocol does not support multiple routing universes then
it SHOULD set the 'Identifier' field according to Table 3. However it SHOULD set the 'Identifier' field according to Table 3. However
an implementation MAY make the 'Identifier' configurable, for a given an implementation MAY make the 'Identifier' configurable, for a given
protocol. protocol.
Each Node Descriptor and Link Descriptor consists of one or more TLVs Each Node Descriptor and Link Descriptor consists of one or more TLVs
described in the following sections. described in the following sections.
skipping to change at page 24, line 14 skipping to change at page 24, line 14
3.3.2.2. MPLS Protocol Mask TLV 3.3.2.2. MPLS Protocol Mask TLV
The MPLS Protocol TLV carries a bit mask describing which MPLS The MPLS Protocol TLV carries a bit mask describing which MPLS
signaling protocols are enabled. The length of this TLV is 1. The signaling protocols are enabled. The length of this TLV is 1. The
value is a bit array of 8 flags, where each bit represents an MPLS value is a bit array of 8 flags, where each bit represents an MPLS
Protocol capability. Protocol capability.
Generation of the MPLS Protocol Mask TLV is only valid for Generation of the MPLS Protocol Mask TLV is only valid for
originators which have local link insight, like for example Protocol- originators which have local link insight, like for example Protocol-
IDs 'Static' or 'Direct' as per Table 2. The MPLS Protocol Mask TLV IDs 'Static' or 'Direct' as per Table 2. The 'MPLS Protocol Mask'
MUST NOT be included in NLRIs with protocol-IDs 'IS-IS L1', 'IS-IS TLV MUST NOT be included in NLRIs with protocol-IDs 'IS-IS L1', 'IS-
L2', 'OSPFv2' or 'OSPFv3' as per Table 2. The 'Protocol Mask' TLV IS L2', 'OSPFv2' or 'OSPFv3' as per Table 2.
MUST NOT be generated in NLRIs with a protocol-ID of 'IS-IS Level 1',
'IS-IS Level 2', 'OSPFv2' or 'OSPFv3'.
0 1 2 3 0 1 2 3
0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
| Type | Length | | Type | Length |
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
|L|R| Reserved | |L|R| Reserved |
+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+
Figure 19: MPLS Protocol TLV Figure 19: MPLS Protocol TLV
skipping to change at page 43, line 29 skipping to change at page 43, line 29
Instance Extensions", RFC 6549, March 2012. Instance Extensions", RFC 6549, March 2012.
[RFC6822] Previdi, S., Ginsberg, L., Shand, M., Roy, A., and D. [RFC6822] Previdi, S., Ginsberg, L., Shand, M., Roy, A., and D.
Ward, "IS-IS Multi-Instance", RFC 6822, December 2012. Ward, "IS-IS Multi-Instance", RFC 6822, December 2012.
11.2. Informative References 11.2. Informative References
[I-D.ietf-idr-error-handling] [I-D.ietf-idr-error-handling]
Chen, E., Scudder, J., Mohapatra, P., and K. Patel, Chen, E., Scudder, J., Mohapatra, P., and K. Patel,
"Revised Error Handling for BGP UPDATE Messages", draft- "Revised Error Handling for BGP UPDATE Messages", draft-
ietf-idr-error-handling-16 (work in progress), November ietf-idr-error-handling-18 (work in progress), December
2014. 2014.
[RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", RFC [RFC4272] Murphy, S., "BGP Security Vulnerabilities Analysis", RFC
4272, January 2006. 4272, January 2006.
[RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation [RFC4655] Farrel, A., Vasseur, J., and J. Ash, "A Path Computation
Element (PCE)-Based Architecture", RFC 4655, August 2006. Element (PCE)-Based Architecture", RFC 4655, August 2006.
[RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S. [RFC4970] Lindem, A., Shen, N., Vasseur, JP., Aggarwal, R., and S.
Shaffer, "Extensions to OSPF for Advertising Optional Shaffer, "Extensions to OSPF for Advertising Optional
 End of changes. 8 change blocks. 
17 lines changed or deleted 15 lines changed or added

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