draft-ietf-rtgwg-enterprise-pa-multihoming-04.txt   draft-ietf-rtgwg-enterprise-pa-multihoming-05.txt 
skipping to change at page 1, line 13 skipping to change at page 1, line 13
Routing Working Group F. Baker Routing Working Group F. Baker
Internet-Draft Internet-Draft
Intended status: Informational C. Bowers Intended status: Informational C. Bowers
Expires: October 15, 2018 Juniper Networks Expires: October 15, 2018 Juniper Networks
J. Linkova J. Linkova
Google Google
April 13, 2018 April 13, 2018
Enterprise Multihoming using Provider-Assigned Addresses without Network Enterprise Multihoming using Provider-Assigned Addresses without Network
Prefix Translation: Requirements and Solution Prefix Translation: Requirements and Solution
draft-ietf-rtgwg-enterprise-pa-multihoming-04 draft-ietf-rtgwg-enterprise-pa-multihoming-05
Abstract Abstract
Connecting an enterprise site to multiple ISPs using provider- Connecting an enterprise site to multiple ISPs using provider-
assigned addresses is difficult without the use of some form of assigned addresses is difficult without the use of some form of
Network Address Translation (NAT). Much has been written on this Network Address Translation (NAT). Much has been written on this
topic over the last 10 to 15 years, but it still remains a problem topic over the last 10 to 15 years, but it still remains a problem
without a clearly defined or widely implemented solution. Any without a clearly defined or widely implemented solution. Any
multihoming solution without NAT requires hosts at the site to have multihoming solution without NAT requires hosts at the site to have
addresses from each ISP and to select the egress ISP by selecting a addresses from each ISP and to select the egress ISP by selecting a
skipping to change at page 3, line 35 skipping to change at page 3, line 35
6. Other Solutions . . . . . . . . . . . . . . . . . . . . . . . 42 6. Other Solutions . . . . . . . . . . . . . . . . . . . . . . . 42
6.1. Shim6 . . . . . . . . . . . . . . . . . . . . . . . . . . 42 6.1. Shim6 . . . . . . . . . . . . . . . . . . . . . . . . . . 42
6.2. IPv6-to-IPv6 Network Prefix Translation . . . . . . . . . 42 6.2. IPv6-to-IPv6 Network Prefix Translation . . . . . . . . . 42
7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42 7. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 42
8. Security Considerations . . . . . . . . . . . . . . . . . . . 43 8. Security Considerations . . . . . . . . . . . . . . . . . . . 43
8.1. Privacy Considerations . . . . . . . . . . . . . . . . . 43 8.1. Privacy Considerations . . . . . . . . . . . . . . . . . 43
9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 43 9. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 43
10. References . . . . . . . . . . . . . . . . . . . . . . . . . 43 10. References . . . . . . . . . . . . . . . . . . . . . . . . . 43
10.1. Normative References . . . . . . . . . . . . . . . . . . 43 10.1. Normative References . . . . . . . . . . . . . . . . . . 43
10.2. Informative References . . . . . . . . . . . . . . . . . 45 10.2. Informative References . . . . . . . . . . . . . . . . . 45
Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 47 Appendix A. Change Log . . . . . . . . . . . . . . . . . . . . . 48
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 47 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 48
1. Introduction 1. Introduction
Site multihoming, the connection of a subscriber network to multiple Site multihoming, the connection of a subscriber network to multiple
upstream networks using redundant uplinks, is a common enterprise upstream networks using redundant uplinks, is a common enterprise
architecture for improving the reliability of its Internet architecture for improving the reliability of its Internet
connectivity. If the site uses provider-independent (PI) addresses, connectivity. If the site uses provider-independent (PI) addresses,
all traffic originating from the enterprise can use source addresses all traffic originating from the enterprise can use source addresses
from the PI address space. Site multihoming with PI addresses is from the PI address space. Site multihoming with PI addresses is
commonly used with both IPv4 and IPv6, and does not present any new commonly used with both IPv4 and IPv6, and does not present any new
skipping to change at page 43, line 13 skipping to change at page 43, line 13
This memo asks the IANA for no new parameters. This memo asks the IANA for no new parameters.
8. Security Considerations 8. Security Considerations
8.1. Privacy Considerations 8.1. Privacy Considerations
9. Acknowledgements 9. Acknowledgements
The original outline was suggested by Ole Troan. The original outline was suggested by Ole Troan.
The authors would like to thank the following people (in alphabetical
order) for their review and feedback: Brian E Carpenter, Lorenzo
Colitti, David Lamparter, Acee Lindem, Philip Matthewsu, Dave Thaler.
10. References 10. References
10.1. Normative References 10.1. Normative References
[RFC1122] Braden, R., Ed., "Requirements for Internet Hosts - [RFC1122] Braden, R., Ed., "Requirements for Internet Hosts -
Communication Layers", STD 3, RFC 1122, Communication Layers", STD 3, RFC 1122,
DOI 10.17487/RFC1122, October 1989, DOI 10.17487/RFC1122, October 1989,
<https://www.rfc-editor.org/info/rfc1122>. <https://www.rfc-editor.org/info/rfc1122>.
[RFC1123] Braden, R., Ed., "Requirements for Internet Hosts - [RFC1123] Braden, R., Ed., "Requirements for Internet Hosts -
 End of changes. 3 change blocks. 
3 lines changed or deleted 7 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/