draft-ietf-ospf-encapsulation-cap-01.txt   draft-ietf-ospf-encapsulation-cap-02.txt 
OSPF Working Group X. Xu, Ed. OSPF Working Group X. Xu, Ed.
Internet-Draft Huawei Internet-Draft Huawei
Intended status: Standards Track B. Decraene, Ed. Intended status: Standards Track B. Decraene, Ed.
Expires: April 16, 2017 Orange Expires: October 23, 2017 Orange
R. Raszuk R. Raszuk
Bloomberg LP Bloomberg LP
U. Chunduri U. Chunduri
Huawei
L. Contreras L. Contreras
Telefonica I+D Telefonica I+D
L. Jalil L. Jalil
Verizon Verizon
October 13, 2016 April 21, 2017
Advertising Tunnelling Capability in OSPF Advertising Tunnelling Capability in OSPF
draft-ietf-ospf-encapsulation-cap-01 draft-ietf-ospf-encapsulation-cap-02
Abstract Abstract
Some networks use tunnels for a variety of reasons. A large variety Some networks use tunnels for a variety of reasons. A large variety
of tunnel types are defined and the ingress needs to select a type of of tunnel types are defined and the ingress needs to select a type of
tunnel which is supported by the egress. This document defines how tunnel which is supported by the egress. This document defines how
to advertise egress tunnel capabilities in OSPF Router Information. to advertise egress tunnel capabilities in OSPF Router Information.
Requirements Language Requirements Language
skipping to change at page 1, line 48 skipping to change at page 1, line 48
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 April 16, 2017. This Internet-Draft will expire on October 23, 2017.
Copyright Notice Copyright Notice
Copyright (c) 2016 IETF Trust and the persons identified as the Copyright (c) 2017 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 2, line 47 skipping to change at page 2, line 47
9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8 9. References . . . . . . . . . . . . . . . . . . . . . . . . . 8
9.1. Normative References . . . . . . . . . . . . . . . . . . 8 9.1. Normative References . . . . . . . . . . . . . . . . . . 8
9.2. Informative References . . . . . . . . . . . . . . . . . 9 9.2. Informative References . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction 1. Introduction
Some networks use tunnels for a variety of reasons, such as: Some networks use tunnels for a variety of reasons, such as:
o Partial deployment of MPLS-SPRING as described in o Partial deployment of MPLS-SPRING as described in
[I-D.xu-mpls-spring-islands-connection-over-ip], where IP tunnels [I-D.xu-mpls-unified-source-routing-instruction], where IP tunnels
are used between MPLS-SPRING-enabled routers so as to traverse are used between MPLS-SPRING-enabled routers so as to traverse
non- MPLS routers. non- MPLS routers.
o Partial deployment of MPLS-BIER as described in Section 6.9 of o Partial deployment of MPLS-BIER as described in Section 6.9 of
[I-D.ietf-bier-architecture], where IP tunnels are used between [I-D.ietf-bier-architecture], where IP tunnels are used between
MPLS-BIER-capable routers so as to traverse non MPLS-BIER MPLS-BIER-capable routers so as to traverse non MPLS-BIER
[I-D.ietf-bier-mpls-encapsulation] routers. [I-D.ietf-bier-mpls-encapsulation] routers.
o Partial deployment of IPv6 (resp. IPv4) in IPv4 (resp. IPv6) o Partial deployment of IPv6 (resp. IPv4) in IPv4 (resp. IPv6)
networks as described in [RFC5565], where IPvx tunnels are used networks as described in [RFC5565], where IPvx tunnels are used
skipping to change at page 9, line 30 skipping to change at page 9, line 30
[RFC7770] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and [RFC7770] Lindem, A., Ed., Shen, N., Vasseur, JP., Aggarwal, R., and
S. Shaffer, "Extensions to OSPF for Advertising Optional S. Shaffer, "Extensions to OSPF for Advertising Optional
Router Capabilities", RFC 7770, DOI 10.17487/RFC7770, Router Capabilities", RFC 7770, DOI 10.17487/RFC7770,
February 2016, <http://www.rfc-editor.org/info/rfc7770>. February 2016, <http://www.rfc-editor.org/info/rfc7770>.
9.2. Informative References 9.2. Informative References
[I-D.ietf-bier-architecture] [I-D.ietf-bier-architecture]
Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and Wijnands, I., Rosen, E., Dolganow, A., Przygienda, T., and
S. Aldrin, "Multicast using Bit Index Explicit S. Aldrin, "Multicast using Bit Index Explicit
Replication", draft-ietf-bier-architecture-04 (work in Replication", draft-ietf-bier-architecture-05 (work in
progress), July 2016. progress), October 2016.
[I-D.ietf-bier-mpls-encapsulation] [I-D.ietf-bier-mpls-encapsulation]
Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J., Wijnands, I., Rosen, E., Dolganow, A., Tantsura, J.,
Aldrin, S., and I. Meilik, "Encapsulation for Bit Index Aldrin, S., and I. Meilik, "Encapsulation for Bit Index
Explicit Replication in MPLS Networks", draft-ietf-bier- Explicit Replication in MPLS and non-MPLS Networks",
mpls-encapsulation-05 (work in progress), July 2016. draft-ietf-bier-mpls-encapsulation-06 (work in progress),
December 2016.
[I-D.ietf-nvo3-vxlan-gpe] [I-D.ietf-nvo3-vxlan-gpe]
Kreeger, L. and U. Elzur, "Generic Protocol Extension for Maino, F., Kreeger, L., and U. Elzur, "Generic Protocol
VXLAN", draft-ietf-nvo3-vxlan-gpe-02 (work in progress), Extension for VXLAN", draft-ietf-nvo3-vxlan-gpe-03 (work
April 2016.
[I-D.xu-mpls-spring-islands-connection-over-ip]
Xu, X., Raszuk, R., Chunduri, U., Contreras, L., and L.
Jalil, "Connecting MPLS-SPRING Islands over IP Networks",
draft-xu-mpls-spring-islands-connection-over-ip-00 (work
in progress), October 2016. in progress), October 2016.
[I-D.xu-mpls-unified-source-routing-instruction]
Xu, X., Bryant, S., Raszuk, R., Chunduri, U., Contreras,
L., Jalil, L., and H. Assarpour, "Unified Source Routing
Instruction using MPLS Label Stack", draft-xu-mpls-
unified-source-routing-instruction-00 (work in progress),
March 2017.
[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,
<http://www.rfc-editor.org/info/rfc2328>. <http://www.rfc-editor.org/info/rfc2328>.
[RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y., [RFC3032] Rosen, E., Tappan, D., Fedorkow, G., Rekhter, Y.,
Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack Farinacci, D., Li, T., and A. Conta, "MPLS Label Stack
Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001, Encoding", RFC 3032, DOI 10.17487/RFC3032, January 2001,
<http://www.rfc-editor.org/info/rfc3032>. <http://www.rfc-editor.org/info/rfc3032>.
[RFC4023] Worster, T., Rekhter, Y., and E. Rosen, Ed., [RFC4023] Worster, T., Rekhter, Y., and E. Rosen, Ed.,
skipping to change at page 11, line 33 skipping to change at page 11, line 33
Orange Orange
Email: bruno.decraene@orange.com Email: bruno.decraene@orange.com
Robert Raszuk Robert Raszuk
Bloomberg LP Bloomberg LP
Email: robert@raszuk.net Email: robert@raszuk.net
Uma Chunduri Uma Chunduri
Huawei
Email: uma.chunduri@gmail.com Email: uma.chunduri@gmail.com
Luis M. Contreras Luis M. Contreras
Telefonica I+D Telefonica I+D
Email: luismiguel.contrerasmurillo@telefonica.com Email: luismiguel.contrerasmurillo@telefonica.com
Luay Jalil Luay Jalil
Verizon Verizon
 End of changes. 12 change blocks. 
19 lines changed or deleted 22 lines changed or added

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