| draft-ietf-bess-mvpn-evpn-aggregation-label-03.txt | draft-ietf-bess-mvpn-evpn-aggregation-label-04.txt | |||
|---|---|---|---|---|
| BESS Z. Zhang | BESS Z. Zhang | |||
| Internet-Draft E. Rosen | Internet-Draft E. Rosen | |||
| Updates: 7432, 6514, 7582 (if approved) W. Lin | Updates: 7432, 6514, 7582 (if approved) W. Lin | |||
| Intended status: Standards Track Juniper Networks | Intended status: Standards Track Juniper Networks | |||
| Expires: April 26, 2020 Z. Li | Expires: May 19, 2021 Z. Li | |||
| Huawei Technologies | Huawei Technologies | |||
| I. Wijnands | I. Wijnands | |||
| Cisco Systems | Cisco Systems | |||
| October 24, 2019 | November 15, 2020 | |||
| MVPN/EVPN Tunnel Aggregation with Common Labels | MVPN/EVPN Tunnel Aggregation with Common Labels | |||
| draft-ietf-bess-mvpn-evpn-aggregation-label-03 | draft-ietf-bess-mvpn-evpn-aggregation-label-04 | |||
| Abstract | Abstract | |||
| The MVPN specifications allow a single Point-to-Multipoint (P2MP) | The MVPN specifications allow a single Point-to-Multipoint (P2MP) | |||
| tunnel to carry traffic of multiple VPNs. The EVPN specifications | tunnel to carry traffic of multiple VPNs. The EVPN specifications | |||
| allow a single P2MP tunnel to carry traffic of multiple Broadcast | allow a single P2MP tunnel to carry traffic of multiple Broadcast | |||
| Domains (BDs). These features require the ingress router of the P2MP | Domains (BDs). These features require the ingress router of the P2MP | |||
| tunnel to allocate an upstream-assigned MPLS label for each VPN or | tunnel to allocate an upstream-assigned MPLS label for each VPN or | |||
| for each BD. A packet sent on a P2MP tunnel then carries the label | for each BD. A packet sent on a P2MP tunnel then carries the label | |||
| that is mapped to its VPN or BD. (In some cases, a distinct | that is mapped to its VPN or BD. (In some cases, a distinct | |||
| skipping to change at page 2, line 20 ¶ | skipping to change at page 2, line 20 ¶ | |||
| 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 26, 2020. | This Internet-Draft will expire on May 19, 2021. | |||
| Copyright Notice | Copyright Notice | |||
| Copyright (c) 2019 IETF Trust and the persons identified as the | Copyright (c) 2020 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 | |||
| skipping to change at page 13, line 19 ¶ | skipping to change at page 13, line 19 ¶ | |||
| [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC | |||
| 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, | |||
| May 2017, <https://www.rfc-editor.org/info/rfc8174>. | May 2017, <https://www.rfc-editor.org/info/rfc8174>. | |||
| 7.2. Informative References | 7.2. Informative References | |||
| [I-D.ietf-bess-evpn-bum-procedure-updates] | [I-D.ietf-bess-evpn-bum-procedure-updates] | |||
| Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A. | Zhang, Z., Lin, W., Rabadan, J., Patel, K., and A. | |||
| Sajassi, "Updates on EVPN BUM Procedures", draft-ietf- | Sajassi, "Updates on EVPN BUM Procedures", draft-ietf- | |||
| bess-evpn-bum-procedure-updates-07 (work in progress), | bess-evpn-bum-procedure-updates-08 (work in progress), | |||
| August 2019. | November 2019. | |||
| [I-D.ietf-bier-evpn] | [I-D.ietf-bier-evpn] | |||
| Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan, | Zhang, Z., Przygienda, T., Sajassi, A., and J. Rabadan, | |||
| "EVPN BUM Using BIER", draft-ietf-bier-evpn-01 (work in | "EVPN BUM Using BIER", draft-ietf-bier-evpn-03 (work in | |||
| progress), April 2018. | progress), April 2020. | |||
| [I-D.ietf-bier-mvpn] | [I-D.ietf-bier-mvpn] | |||
| Rosen, E., Sivakumar, M., Aldrin, S., Dolganow, A., and T. | Rosen, E., Sivakumar, M., Aldrin, S., Dolganow, A., and T. | |||
| Przygienda, "Multicast VPN Using BIER", draft-ietf-bier- | Przygienda, "Multicast VPN Using BIER", draft-ietf-bier- | |||
| mvpn-11 (work in progress), March 2018. | mvpn-11 (work in progress), March 2018. | |||
| [I-D.ietf-spring-segment-routing] | [I-D.ietf-spring-segment-routing] | |||
| Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., | Filsfils, C., Previdi, S., Ginsberg, L., Decraene, B., | |||
| Litkowski, S., and R. Shakir, "Segment Routing | Litkowski, S., and R. Shakir, "Segment Routing | |||
| Architecture", draft-ietf-spring-segment-routing-15 (work | Architecture", draft-ietf-spring-segment-routing-15 (work | |||
| End of changes. 7 change blocks. | ||||
| 9 lines changed or deleted | 9 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/ | ||||