draft-ietf-ospf-xaf-te-01.txt   draft-ietf-ospf-xaf-te-02.txt 
OSPF A. Smirnov LSR A. Smirnov
Internet-Draft A. Retana Internet-Draft Cisco Systems, Inc.
Updates: 5786 (if approved) M. Barnes Updates: 5786 (if approved) A. Retana
Intended status: Standards Track Cisco Systems, Inc. Intended status: Standards Track Huawei R&D USA
Expires: April 18, 2018 October 15, 2017 Expires: October 20, 2018 M. Barnes
Cisco Systems, Inc.
April 18, 2018
OSPF Routing with Cross-Address Family MPLS Traffic Engineering Tunnels OSPF Routing with Cross-Address Family Traffic Engineering Tunnels
draft-ietf-ospf-xaf-te-01 draft-ietf-ospf-xaf-te-02
Abstract Abstract
When using Traffic Engineering (TE) in a dual-stack IPv4/IPv6 network When using Traffic Engineering (TE) in a dual-stack IPv4/IPv6 network
the Multiprotocol Label Switching (MPLS) TE Label Switched Paths the Multiprotocol Label Switching (MPLS) TE Label Switched Paths
(LSP) infrastructure may be duplicated, even if the destination IPv4 (LSP) infrastructure may be duplicated, even if the destination IPv4
and IPv6 addresses belong to the same remote router. In order to and IPv6 addresses belong to the same remote router. In order to
achieve an integrated MPLS TE LSP infrastructure, OSPF routes must be achieve an integrated MPLS TE LSP infrastructure, OSPF routes must be
computed over MPLS TE tunnels created using information propagated in computed over MPLS TE tunnels created using information propagated in
another OSPF instance. This is solved by advertising cross-address another OSPF instance. This is solved by advertising cross-address
skipping to change at page 1, line 41 skipping to change at page 1, line 43
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 https://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 April 18, 2018. This Internet-Draft will expire on October 20, 2018.
Copyright Notice Copyright Notice
Copyright (c) 2017 IETF Trust and the persons identified as the Copyright (c) 2018 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
(https://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 . . . . . . . . . . . . . . . . . . . . . . . . 2 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3
3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 3 3. Operation . . . . . . . . . . . . . . . . . . . . . . . . . . 4
4. Backward Compatibility . . . . . . . . . . . . . . . . . . . 5 4. Backward Compatibility . . . . . . . . . . . . . . . . . . . 5
5. Security Considerations . . . . . . . . . . . . . . . . . . . 6 5. Security Considerations . . . . . . . . . . . . . . . . . . . 6
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6 6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 6
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6 7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 6
8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6 8. References . . . . . . . . . . . . . . . . . . . . . . . . . 6
8.1. Normative References . . . . . . . . . . . . . . . . . . 6 8.1. Normative References . . . . . . . . . . . . . . . . . . 6
8.2. Informative References . . . . . . . . . . . . . . . . . 7 8.2. Informative References . . . . . . . . . . . . . . . . . 7
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 7
1. Introduction 1. Introduction
skipping to change at page 3, line 42 skipping to change at page 3, line 45
The method described in this document can also be used to compute The method described in this document can also be used to compute
X-AF mapping of egress LSR for sub-LSPs of a Point-to-Multipoint LSP X-AF mapping of egress LSR for sub-LSPs of a Point-to-Multipoint LSP
(see [RFC4461]). Considerations of using Point-to-Multipoint MPLS TE (see [RFC4461]). Considerations of using Point-to-Multipoint MPLS TE
for X-AF traffic forwarding is outside the scope of this for X-AF traffic forwarding is outside the scope of this
specification. specification.
2. Requirements Language 2. Requirements Language
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and
document are to be interpreted as described in [RFC2119]. "OPTIONAL" in this document are to be interpreted as described in BCP
14 [RFC2119] [RFC8174] when, and only when, they appear in all
capitals, as shown here.
3. Operation 3. Operation
[RFC5786] defined the Node IPv4 Local Address and Node IPv6 Local [RFC5786] defined the Node IPv4 Local Address and Node IPv6 Local
Address sub-TLVs of the Node Attribute TLV for a router to advertise Address sub-TLVs of the Node Attribute TLV for a router to advertise
additional local IPv4 and IPv6 addresses. To solve the problem additional local IPv4 and IPv6 addresses. To solve the problem
outlined in [RFC5786] OSPFv2 would advertise and use only IPv4 outlined in [RFC5786] OSPFv2 would advertise and use only IPv4
addresses and OSPFv3 would advertise and use only IPv6 addresses. addresses and OSPFv3 would advertise and use only IPv6 addresses.
This document updates [RFC5786] so that a router can also announce This document updates [RFC5786] so that a router can also announce
skipping to change at page 7, line 5 skipping to change at page 7, line 10
[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, Requirement Levels", BCP 14, RFC 2119,
DOI 10.17487/RFC2119, March 1997, DOI 10.17487/RFC2119, March 1997,
<https://www.rfc-editor.org/info/rfc2119>. <https://www.rfc-editor.org/info/rfc2119>.
[RFC5786] Aggarwal, R. and K. Kompella, "Advertising a Router's [RFC5786] Aggarwal, R. and K. Kompella, "Advertising a Router's
Local Addresses in OSPF Traffic Engineering (TE) Local Addresses in OSPF Traffic Engineering (TE)
Extensions", RFC 5786, DOI 10.17487/RFC5786, March 2010, Extensions", RFC 5786, DOI 10.17487/RFC5786, March 2010,
<https://www.rfc-editor.org/info/rfc5786>. <https://www.rfc-editor.org/info/rfc5786>.
[RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC
2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174,
May 2017, <https://www.rfc-editor.org/info/rfc8174>.
8.2. Informative References 8.2. Informative References
[RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328, [RFC2328] Moy, J., "OSPF Version 2", STD 54, RFC 2328,
DOI 10.17487/RFC2328, April 1998, DOI 10.17487/RFC2328, April 1998,
<https://www.rfc-editor.org/info/rfc2328>. <https://www.rfc-editor.org/info/rfc2328>.
[RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering [RFC3630] Katz, D., Kompella, K., and D. Yeung, "Traffic Engineering
(TE) Extensions to OSPF Version 2", RFC 3630, (TE) Extensions to OSPF Version 2", RFC 3630,
DOI 10.17487/RFC3630, September 2003, DOI 10.17487/RFC3630, September 2003,
<https://www.rfc-editor.org/info/rfc3630>. <https://www.rfc-editor.org/info/rfc3630>.
skipping to change at page 7, line 37 skipping to change at page 8, line 4
for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008,
<https://www.rfc-editor.org/info/rfc5340>. <https://www.rfc-editor.org/info/rfc5340>.
[RFC6827] Malis, A., Ed., Lindem, A., Ed., and D. Papadimitriou, [RFC6827] Malis, A., Ed., Lindem, A., Ed., and D. Papadimitriou,
Ed., "Automatically Switched Optical Network (ASON) Ed., "Automatically Switched Optical Network (ASON)
Routing for OSPFv2 Protocols", RFC 6827, Routing for OSPFv2 Protocols", RFC 6827,
DOI 10.17487/RFC6827, January 2013, DOI 10.17487/RFC6827, January 2013,
<https://www.rfc-editor.org/info/rfc6827>. <https://www.rfc-editor.org/info/rfc6827>.
Authors' Addresses Authors' Addresses
Anton Smirnov Anton Smirnov
Cisco Systems, Inc. Cisco Systems, Inc.
De kleetlaan 6a De kleetlaan 6a
Diegem 1831 Diegem 1831
Belgium Belgium
Email: as@cisco.com Email: as@cisco.com
Alvaro Retana Alvaro Retana
Cisco Systems, Inc. Huawei R&D USA
7025 Kit Creek Rd. 2330 Central Expressway
Research Triangle Park, NC 27709 Santa Clara, CA 95050
USA USA
Email: aretana@cisco.com Email: alvaro.retana@huawei.com
Michael Barnes Michael Barnes
Cisco Systems, Inc. Cisco Systems, Inc.
510 McCarthy Blvd. 510 McCarthy Blvd.
Milpitas, CA 95035 Milpitas, CA 95035
USA USA
Email: mjbarnes@cisco.com Email: mjbarnes@cisco.com
 End of changes. 11 change blocks. 
17 lines changed or deleted 25 lines changed or added

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