| draft-ietf-idr-sdwan-edge-discovery-02.txt | draft-ietf-idr-sdwan-edge-discovery-03.txt | |||
|---|---|---|---|---|
| Network Working Group L. Dunbar | Network Working Group L. Dunbar | |||
| Internet Draft Futurewei | Internet Draft Futurewei | |||
| Intended status: Standard S. Hares | Intended status: Standard S. Hares | |||
| Expires: October 26, 2022 Hickory Hill Consulting | Expires: December 28, 2022 Hickory Hill Consulting | |||
| R. Raszuk | R. Raszuk | |||
| NTT Network Innovations | NTT Network Innovations | |||
| K. Majumdar | K. Majumdar | |||
| CommScope | Microsoft | |||
| Gyan Mishra | Gyan Mishra | |||
| Verizon | Verizon | |||
| April 26, 2022 | June 28, 2022 | |||
| BGP UPDATE for SDWAN Edge Discovery | BGP UPDATE for SDWAN Edge Discovery | |||
| draft-ietf-idr-sdwan-edge-discovery-02 | draft-ietf-idr-sdwan-edge-discovery-03 | |||
| Abstract | Abstract | |||
| The document describes the encoding of BGP UPDATE messages for the | The document describes the encoding of BGP UPDATE messages for the | |||
| SDWAN edge node discovery. | SDWAN edge node discovery. | |||
| In the context of this document, BGP Route Reflector (RR) is the | In the context of this document, BGP Route Reflector (RR) is the | |||
| component of the SDWAN Controller that receives the BGP UPDATE from | component of the SDWAN Controller that receives the BGP UPDATE from | |||
| SDWAN edges and in turns propagates the information to the intended | SDWAN edges and in turns propagates the information to the intended | |||
| peers that are authorized to communicate via the SDWAN overlay | peers that are authorized to communicate via the SDWAN overlay | |||
| skipping to change at page 2, line 10 ¶ | skipping to change at page 2, line 10 ¶ | |||
| Internet-Drafts are draft documents valid for a maximum of six | Internet-Drafts are draft documents valid for a maximum of six | |||
| months and may be updated, replaced, or obsoleted by other documents | months and may be updated, replaced, or obsoleted by other documents | |||
| at any time. It is inappropriate to use Internet-Drafts as | at any time. It is inappropriate to use Internet-Drafts as | |||
| reference material or to cite them other than as "work in progress." | reference material or to cite them other than as "work in progress." | |||
| The list of current Internet-Drafts can be accessed at | The list of current Internet-Drafts can be accessed at | |||
| http://www.ietf.org/ietf/1id-abstracts.txt | http://www.ietf.org/ietf/1id-abstracts.txt | |||
| The list of Internet-Draft Shadow Directories can be accessed at | The list of Internet-Draft Shadow Directories can be accessed at | |||
| http://www.ietf.org/shadow.html | http://www.ietf.org/shadow.html | |||
| This Internet-Draft will expire on Dec 25, 2022. | This Internet-Draft will expire on Dec 21, 2022. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2022 IETF Trust and the persons identified as the | Copyright (c) 2022 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 13, line 24 ¶ | skipping to change at page 13, line 24 ¶ | |||
| For an SDWAN edge node which can be reached by both MPLS and IPsec | For an SDWAN edge node which can be reached by both MPLS and IPsec | |||
| paths, the client packets reached by MPLS network will be encoded | paths, the client packets reached by MPLS network will be encoded | |||
| with the MPLS Labels based on the scheme specified by [RFC8277]. | with the MPLS Labels based on the scheme specified by [RFC8277]. | |||
| For GRE Encapsulation within an IPsec tunnel, the GRE key field can | For GRE Encapsulation within an IPsec tunnel, the GRE key field can | |||
| be used to carry the SDWAN VPN ID. For network virtual overlay | be used to carry the SDWAN VPN ID. For network virtual overlay | |||
| (VxLAN, GENEVE, etc.) encapsulation within the IPsec tunnel, the | (VxLAN, GENEVE, etc.) encapsulation within the IPsec tunnel, the | |||
| Virtual Network Identifier (VNI) field is used to carry the SDWAN | Virtual Network Identifier (VNI) field is used to carry the SDWAN | |||
| VPN ID. | VPN ID. | |||
| 6. Hybrid Underlay Tunnel UPDATE | 6. Hybrid Tunnel UPDATE | |||
| The hybrid underlay tunnel UPDATE is to advertise the detailed | The hybrid underlay tunnel UPDATE is to advertise the detailed | |||
| properties of hybrid types of tunnels terminated at a SDWAN edge | properties of hybrid types of tunnels terminated at a SDWAN edge | |||
| node. | node. | |||
| A client route UDPATE is recursively tied to an underlay tunnel | A client route UDPATE is recursively tied to an underlay tunnel | |||
| UDPATE by the Color Extended Community included in client route | UDPATE by the Color Extended Community included in client route | |||
| UPDATE. | UPDATE. | |||
| 6.1. NLRI for Hybrid Underlay Tunnel Update | 6.1. NLRI for Hybrid Underlay Tunnel Update | |||
| A new NLRI is introduced within the MP_REACH_NLRI Path Attribute of | A new NLRI is introduced within the MP_REACH_NLRI Path Attribute of | |||
| RFC4760, for advertising the detailed properties of hybrid types of | RFC4760, for advertising the detailed properties of hybrid types of | |||
| tunnels terminated at the edge node, with SAFI=SDWAN (code = 74): | tunnels terminated at the edge node, with SAFI=SDWAN (code = 74): | |||
| +------------------+ | +------------------+ | |||
| | NLRI Length | 1 octet | | NLRI Length | 1 octet | |||
| +------------------+ | +------------------+ | |||
| | Site-Type | 2 Octet | | Topology-Type | 2 Octet | |||
| +------------------+ | +------------------+ | |||
| | Port-Local-ID | 4 octets | | Port-Local-ID | 4 octets | |||
| +------------------+ | +------------------+ | |||
| | SDWAN-Color | 4 octets | | SDWAN-Color | 4 octets | |||
| +------------------+ | +------------------+ | |||
| | SDWAN-Node-ID | 4 or 16 octets | | SDWAN-Node-ID | 4 or 16 octets | |||
| +------------------+ | +------------------+ | |||
| where: | where: | |||
| - NLRI Length: 1 octet of length expressed in bits as defined in | - NLRI Length: 1 octet of length expressed in bits as defined in | |||
| [RFC4760]. | [RFC4760]. | |||
| - Site Type: 2 octet value. The SDWAN Site Type defines the | - Topology Type: 2 octet value. The SDWAN Site Type defines the | |||
| different types of Site IDs to be used in the deployment. This | different types of Site IDs to be used in the deployment. This | |||
| document defines the following types: | document defines the following types: | |||
| Site-Type = 1: For a simple deployment, such as all edge | Topology-Type = 1: For a simple deployment, such as all edge | |||
| nodes under one SDWAN management system, the node ID is | nodes under one SDWAN management system, the node ID is | |||
| enough for the SDWAN management to map the site to its | enough for the SDWAN management to map the site to its | |||
| precise geolocation. | precise geolocation. | |||
| Site-Type = 2: For large SDWAN heterogeneous deployment where | Topology-Type = 2: For large SDWAN heterogeneous deployment | |||
| a Geo-Loc Sub-TLV [LISP-GEOLoc]is needed to fully describe | where a Geo-Loc Sub-TLV [LISP-GEOLoc]is needed to fully | |||
| the accurate location of the node. | describe the accurate location of the node. | |||
| - Port local ID: SDWAN edge node Port identifier, which is locally | - Port local ID: SDWAN edge node Port identifier, which is locally | |||
| significant. If the SDWAN NLRI applies to multiple ports, this | significant. If the SDWAN NLRI applies to multiple ports, this | |||
| field is NULL. | field is NULL. | |||
| - SDWAN-Color: to correlate with the Color-Extended-community | - SDWAN-Color: to correlate with the Color-Extended-community | |||
| included in the client routes UPDATE. | included in the client routes UPDATE. | |||
| - SDWAN Edge Node ID: The node's IPv4 or IPv6 address. | - SDWAN Edge Node ID: The node's IPv4 or IPv6 address. | |||
| 6.2. SDWAN-Hybrid Tunnel Encoding | 6.2. SDWAN-Hybrid Tunnel Encoding | |||
| A new BGP Tunnel-Type=SDWAN-Hybrid (code point TBD1) is specified | A new BGP Tunnel-Type=SDWAN-Hybrid (code point TBD1) is specified | |||
| skipping to change at page 31, line 20 ¶ | skipping to change at page 31, line 20 ¶ | |||
| Sue Hares | Sue Hares | |||
| Hickory Hill Consulting | Hickory Hill Consulting | |||
| Email: shares@ndzh.com | Email: shares@ndzh.com | |||
| Robert Raszuk | Robert Raszuk | |||
| NTT Network Innovations | NTT Network Innovations | |||
| Email: robert@raszuk.net | Email: robert@raszuk.net | |||
| Kausik Majumdar | Kausik Majumdar | |||
| CommScope | Microsoft | |||
| Email: Kausik.Majumdar@commscope.com | Email: kmajumdar@microsoft.com | |||
| Gyan Mishra | Gyan Mishra | |||
| Verizon Inc. | Verizon Inc. | |||
| Email: gyan.s.mishra@verizon.com | Email: gyan.s.mishra@verizon.com | |||
| Contributors' Addresses | Contributors' Addresses | |||
| Donald Eastlake | Donald Eastlake | |||
| Futurewei | Futurewei | |||
| Email: d3e3e3@gmail.com | Email: d3e3e3@gmail.com | |||
| End of changes. 11 change blocks. | ||||
| 14 lines changed or deleted | 14 lines changed or added | |||
This html diff was produced by rfcdiff 1.48. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ | ||||