ISIS Extensions for Broadcast Inter-AS TE Link
draft-chen-isis-ias-lk-01
|
| Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2017-09-11
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
pdf
html
bibtex
|
| Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
| IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
ISIS Working Group H. Chen
Internet-Draft Huawei Technologies
Intended status: Standards Track M. Toy
Expires: March 15, 2018 Verizon
X. Liu
Jabil
L. Liu
Fujitsu
Z. Li
China Mobile
Y. Yang
Sockrate
September 11, 2017
ISIS Extensions for Broadcast Inter-AS TE Link
draft-chen-isis-ias-lk-01
Abstract
This document presents extensions to the ISIS protocol for
advertising broadcast inter-AS Traffic Engineering (TE) links.
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at http://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on March 15, 2018.
Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(http://trustee.ietf.org/license-info) in effect on the date of
Chen, et al. Expires March 15, 2018 [Page 1]
Internet-Draft inter-as-te-link September 2017
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3
2. Conventions Used in This Document . . . . . . . . . . . . . . . 3
3. Information on Inter-AS TE Link . . . . . . . . . . . . . . . . 3
4. Extensions to ISIS . . . . . . . . . . . . . . . . . . . . . . 4
4.1. sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . . 4
4.2.1. ISIS Router Procedure . . . . . . . . . . . . . . . . . 5
4.2.2. Super Node Procedure . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . . 6
Chen, et al. Expires March 15, 2018 [Page 2]
Internet-Draft inter-as-te-link September 2017
1. Introduction
Connections among different Autonomous Systems (ASes) may be point-
to-point (P2P) links and broadcast links. For a P2P inter-AS TE
link, RFC 5316 defines a new TLV, the inter-AS reachability TLV, for
advertising the link.
It also defines three new sub-TLVs for inclusion in the inter-AS
reachability TLV to carry the information about the neighboring AS
number and the remote ASBR ID of an inter-AS link.
For a P2P inter-AS link, the information about its remote ASBR may be
configured. For a broadcast inter-AS link, no item configured
corresponds to the designated router (DR) of the link in ISIS. Since
no ISIS runs over any broadcast inter-AS link, no DR is selected. It
is hard to configure an item corresponding to the DR on a broadcast
Show full document text