draft-ietf-idr-ls-distribution-08.txt   draft-ietf-idr-ls-distribution-09.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: July 24, 2015 S. Previdi Expires: July 25, 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.
January 20, 2015 January 21, 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-08 draft-ietf-idr-ls-distribution-09
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 July 24, 2015. This Internet-Draft will expire on July 25, 2015.
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 21, line 30 skipping to change at page 21, line 30
Figure 16: IS-IS Area Identifier TLV Format Figure 16: IS-IS Area Identifier TLV Format
3.3.1.3. Node Name TLV 3.3.1.3. Node Name TLV
The Node Name TLV is optional. Its structure and encoding has been The Node Name TLV is optional. Its structure and encoding has been
borrowed from [RFC5301]. The value field identifies the symbolic borrowed from [RFC5301]. The value field identifies the symbolic
name of the router node. This symbolic name can be the FQDN for the name of the router node. This symbolic name can be the FQDN for the
router, it can be a subset of the FQDN, or it can be any string router, it can be a subset of the FQDN, or it can be any string
operators want to use for the router. The use of FQDN or a subset of operators want to use for the router. The use of FQDN or a subset of
it is strongly RECOMMENDED. it is strongly RECOMMENDED. The maximum length of the 'Node Name
TLV' is 255 octets.
The Value field is encoded in 7-bit ASCII. If a user-interface for The Value field is encoded in 7-bit ASCII. If a user-interface for
configuring or displaying this field permits Unicode characters, that configuring or displaying this field permits Unicode characters, that
user-interface is responsible for applying the ToASCII and/or user-interface is responsible for applying the ToASCII and/or
ToUnicode algorithm as described in [RFC5890] to achieve the correct ToUnicode algorithm as described in [RFC5890] to achieve the correct
format for transmission or display. format for transmission or display.
Although [RFC5301] is an IS-IS specific extension, usage of the Node Although [RFC5301] is an IS-IS specific extension, usage of the Node
Name TLV is possible for all protocols. How a router derives and Name TLV is possible for all protocols. How a router derives and
injects node names for e.g. OSPF nodes, is outside of the scope of injects node names for e.g. OSPF nodes, is outside of the scope of
skipping to change at page 27, line 5 skipping to change at page 27, line 5
+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+
Figure 23: Opaque link attribute format Figure 23: Opaque link attribute format
3.3.2.7. Link Name TLV 3.3.2.7. Link Name TLV
The Link Name TLV is optional. The value field identifies the The Link Name TLV is optional. The value field identifies the
symbolic name of the router link. This symbolic name can be the FQDN symbolic name of the router link. This symbolic name can be the FQDN
for the link, it can be a subset of the FQDN, or it can be any string for the link, it can be a subset of the FQDN, or it can be any string
operators want to use for the link. The use of FQDN or a subset of operators want to use for the link. The use of FQDN or a subset of
it is strongly RECOMMENDED. it is strongly RECOMMENDED. The maximum length of the 'Link Name
TLV' is 255 octets.
The Value field is encoded in 7-bit ASCII. If a user-interface for The Value field is encoded in 7-bit ASCII. If a user-interface for
configuring or displaying this field permits Unicode characters, that configuring or displaying this field permits Unicode characters, that
user-interface is responsible for applying the ToASCII and/or user-interface is responsible for applying the ToASCII and/or
ToUnicode algorithm as described in [RFC5890] to achieve the correct ToUnicode algorithm as described in [RFC5890] to achieve the correct
format for transmission or display. format for transmission or display.
How a router derives and injects link names is outside of the scope How a router derives and injects link names is outside of the scope
of this document. of this document.
 End of changes. 6 change blocks. 
6 lines changed or deleted 8 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/