< draft-chen-isis-ias-lk-02.txt   draft-chen-isis-ias-lk-03.txt >
ISIS Working Group H. Chen ISIS Working Group H. Chen
Internet-Draft Huawei Technologies Internet-Draft Futurewei
Intended status: Standards Track M. Toy Intended status: Standards Track M. Toy
Expires: September 6, 2018 Verizon Expires: January 9, 2020 Verizon
X. Liu X. Liu
Jabil Volta Networks
L. Liu L. Liu
Fujitsu Fujitsu
Z. Li Z. Li
China Mobile China Mobile
Y. Yang Y. Yang
Sockrate IBM
March 5, 2018 July 8, 2019
ISIS Extensions for Broadcast Inter-AS TE Link ISIS Extensions for Broadcast Inter-AS TE Link
draft-chen-isis-ias-lk-02 draft-chen-isis-ias-lk-03
Abstract Abstract
This document presents extensions to the ISIS protocol for This document presents extensions to the ISIS protocol for
advertising broadcast inter-AS Traffic Engineering (TE) links. advertising broadcast inter-AS Traffic Engineering (TE) links.
Status of This Memo Status of This Memo
This Internet-Draft is submitted in full conformance with the This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79. provisions of BCP 78 and BCP 79.
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 https://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 September 6, 2018. This Internet-Draft will expire on January 9, 2020.
Copyright Notice Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the Copyright (c) 2019 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 (https://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
described in the Simplified BSD License. described in the Simplified BSD License.
Table of Contents Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 3 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Conventions Used in This Document . . . . . . . . . . . . . . . 3 2. Conventions Used in This Document . . . . . . . . . . . . . . 3
3. Information on Inter-AS TE Link . . . . . . . . . . . . . . . . 3 3. Information on Inter-AS TE Link . . . . . . . . . . . . . . . 3
4. Extensions to ISIS . . . . . . . . . . . . . . . . . . . . . . 4 4. Extensions to ISIS . . . . . . . . . . . . . . . . . . . . . 3
4.1. sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . . 4 4.1. sub-TLVs . . . . . . . . . . . . . . . . . . . . . . . . 3
4.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . . 4 4.2. Procedures . . . . . . . . . . . . . . . . . . . . . . . 4
4.2.1. ISIS Router Procedure . . . . . . . . . . . . . . . . . 5 4.2.1. ISIS Router Procedure . . . . . . . . . . . . . . . . 4
4.2.2. Super Node Procedure . . . . . . . . . . . . . . . . . 5 4.2.2. Super Node Procedure . . . . . . . . . . . . . . . . 4
5. Security Considerations . . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 5
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 5
7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgement . . . . . . . . . . . . . . . . . . . . . . . 5
8. References . . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 5
8.1. Normative References . . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 5
8.2. Informative References . . . . . . . . . . . . . . . . . . 6 8.2. Informative References . . . . . . . . . . . . . . . . . 6
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 6
1. Introduction 1. Introduction
Connections among different Autonomous Systems (ASes) may be point- Connections among different Autonomous Systems (ASes) may be point-
to-point (P2P) links and broadcast links. For a P2P inter-AS TE 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 link, RFC 5316 defines a new TLV, the inter-AS reachability TLV, for
advertising the link. advertising the link.
It also defines three new sub-TLVs for inclusion in the inter-AS It also defines three new sub-TLVs for inclusion in the inter-AS
reachability TLV to carry the information about the neighboring AS reachability TLV to carry the information about the neighboring AS
skipping to change at page 5, line 33 skipping to change at page 5, line 8
Suppose that there is a super node, which just receives LSPs from Suppose that there is a super node, which just receives LSPs from
each of ASes (or domains) through a passive ISIS adjacency between each of ASes (or domains) through a passive ISIS adjacency between
the super node and an ASBR or a normal router in the AS or domain. the super node and an ASBR or a normal router in the AS or domain.
For a new broadcast link connecting multiple routers, when the super For a new broadcast link connecting multiple routers, when the super
node receives an LSP containing the link attached to router X, it node receives an LSP containing the link attached to router X, it
stores the link from X into its TED. It finds the link's remote end stores the link from X into its TED. It finds the link's remote end
P using the link's local IP address with network mask. P is a Pseudo P using the link's local IP address with network mask. P is a Pseudo
node identified by the local IP address of the DR selected from the node identified by the local IP address of the DR selected from the
routers connected to the link. After finding P, it associates the routers connected to the link. After finding P, it associates the
link attached to X with P and the link connected to P with X. If P is link attached to X with P and the link connected to P with X. If P
not found, a new Pseudo node P is created. The super node associates is not found, a new Pseudo node P is created. The super node
the link attached to X with P and the link attached to P with X. This associates the link attached to X with P and the link attached to P
creates a bidirectional connection between X and P. with X. This creates a bidirectional connection between X and P.
The first router and second router from which the super node receives The first router and second router from which the super node receives
an LSP containing the link are selected as the DR and BDR an LSP containing the link are selected as the DR and BDR
respectively. After the DR is down, the BDR becomes the DR and the respectively. After the DR is down, the BDR becomes the DR and the
router other than the DR with the largest (or smallest) local IP router other than the DR with the largest (or smallest) local IP
address connecting to the link is selected as the BDR. address connecting to the link is selected as the BDR.
When the old DR is down and the BDR becomes the new DR, the super When the old DR is down and the BDR becomes the new DR, the super
node updates its TED through removing the link between each of node updates its TED through removing the link between each of
routers X and old P (the Pseudo node corresponding to the old DR) and routers X and old P (the Pseudo node corresponding to the old DR) and
skipping to change at page 6, line 24 skipping to change at page 5, line 45
7. Acknowledgement 7. Acknowledgement
The authors would like to thank all for their valuable comments on The authors would like to thank all for their valuable comments on
this draft. this draft.
8. References 8. References
8.1. Normative References 8.1. Normative References
[RFC2119] Bradner, S., "Key words for use in RFCs to Indicate [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate
Requirement Levels", BCP 14, RFC 2119, DOI 10.17487/ Requirement Levels", BCP 14, RFC 2119,
RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in [RFC5316] Chen, M., Zhang, R., and X. Duan, "ISIS Extensions in
Support of Inter-Autonomous System (AS) MPLS and GMPLS Support of Inter-Autonomous System (AS) MPLS and GMPLS
Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316, Traffic Engineering", RFC 5316, DOI 10.17487/RFC5316,
December 2008, <https://www.rfc-editor.org/info/rfc5316>. December 2008, <https://www.rfc-editor.org/info/rfc5316>.
[RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic [RFC5305] Li, T. and H. Smit, "IS-IS Extensions for Traffic
Engineering", RFC 5305, DOI 10.17487/RFC5305, Engineering", RFC 5305, DOI 10.17487/RFC5305, October
October 2008, <https://www.rfc-editor.org/info/rfc5305>. 2008, <https://www.rfc-editor.org/info/rfc5305>.
8.2. Informative References 8.2. Informative References
[RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the [RFC6805] King, D., Ed. and A. Farrel, Ed., "The Application of the
Path Computation Element Architecture to the Determination Path Computation Element Architecture to the Determination
of a Sequence of Domains in MPLS and GMPLS", RFC 6805, of a Sequence of Domains in MPLS and GMPLS", RFC 6805,
DOI 10.17487/RFC6805, November 2012, DOI 10.17487/RFC6805, November 2012,
<https://www.rfc-editor.org/info/rfc6805>. <https://www.rfc-editor.org/info/rfc6805>.
Authors' Addresses Authors' Addresses
Huaimo Chen Huaimo Chen
Huawei Technologies Futurewei
Boston, MA, Boston, MA
USA USA
EMail: Huaimo.chen@huawei.com EMail: hchen@futurewei.com
Mehmet Toy Mehmet Toy
Verizon Verizon
USA USA
EMail: mehmet.toy@verizon.com EMail: mehmet.toy@verizon.com
Xufeng Liu Xufeng Liu
Jabil Volta Networks
McLean, VA McLean, VA
USA USA
EMail: Xufeng_Liu@jabil.com EMail: xufeng.liu.ietf@gmail.com
Lei Liu Lei Liu
Fujitsu Fujitsu
USA USA
EMail: lliu@us.fujitsu.com EMail: liulei.kddi@gmail.com
Zhenqiang Li Zhenqiang Li
China Mobile China Mobile
No.32 Xuanwumenxi Ave., Xicheng District No.32 Xuanwumenxi Ave., Xicheng District
Beijing 100032 Beijing 100032
P.R. China P.R. China
EMail: li_zhenqiang@hotmail.com EMail: li_zhenqiang@hotmail.com
Yi Yang Yi Yang
Sockrate IBM
NC NC
USA USA
EMail: yyang1998@gmail.com EMail: yyang1998@gmail.com
 End of changes. 19 change blocks. 
40 lines changed or deleted 40 lines changed or added

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