| Internet-Draft | OHT-MH | July 2024 |
| Matsuhira | Expires 7 January 2025 | [Page] |
This document describes how to achieve multihoming using OHT. This document describes both the use of provider addresses and provider independent addresses.¶
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119 [RFC2119].¶
This Internet-Draft is submitted in full conformance with the provisions of BCP 78 and BCP 79.¶
Internet-Drafts are working documents of the Internet Engineering Task Force (IETF). Note that other groups may also distribute working documents as Internet-Drafts. The list of current Internet-Drafts is at https://datatracker.ietf.org/drafts/current/.¶
Internet-Drafts are draft documents valid for a maximum of six months and may be updated, replaced, or obsoleted by other documents at any time. It is inappropriate to use Internet-Drafts as reference material or to cite them other than as "work in progress."¶
This Internet-Draft will expire on 7 January 2025.¶
Copyright (c) 2024 IETF Trust and the persons identified as the document authors. All rights reserved.¶
This document is subject to BCP 78 and the IETF Trust's Legal Provisions Relating to IETF Documents (https://trustee.ietf.org/license-info) in effect on the date of publication of this document. Please review these documents carefully, as they describe your rights and restrictions with respect to this document. Code Components extracted from this document must include Revised BSD License text as described in Section 4.e of the Trust Legal Provisions and are provided without warranty as described in the Revised BSD License.¶
This document describes how to achieve multihoming using OHT [I-D.matsuhira-oht]. This document describes both the use of provider addresses and provider independent addresses.¶
This section describes multihoming configuration with OHT.¶
+--------+
| Server |
+--------+
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/ The Internet /
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
+---* +---+
~~|OHT|~~~ ~~|OHT|~~~
/ |P1 | / / |P2 | /
/ +---+ / / +---+ /
/ ISP / / ISP /
/ #1 / / #2 /
~~~~~~~~~~~ ~~~~~~~~~~
| |
+-----+ +-----+
| OHT | | OHT |
| C1 | | C2 |
+--+--+ +--+--+
| |
-----+-----------------------------------
| PA(#1)
+---+--*
| HOST |
+------*
HOST ------------> OHT C1 ------------> OHT P1 -----------> Server
+-----------+ +-----------+ +-----------+
| IP | data | | IP | data | | IP | data |
+-----------+ +-----------+ +-----------+
src: PA(#1) src: PA(#1) src: PA(#1)
dst: Server dst: Server dst: Server
HOST ------------> OHT C1 -----------> OHT C2 -----------> OHT P2
+-----------+ +----------------+ +----------------+
| IP | data | | IP | IP | data | | IP | IP | data |
+-----------+ +----------------+ +----------------+
src: PA(#1) src: C1 src: C2
dst: Server dst: C2 dst: P2
OHT P2 ------------> OHT P1 -------------> Server
+---------------+ +-----------+
| IP | IP |data | | IP | data |
+---------------+ +-----------+
src: P2 src: PA(#1)
dst: P1 dst: Server
+--------+
| Server |
+--------+
|
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/ The Internet /
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
| |
+---* +---+
~~|OHT|~~~ ~~|OHT|~~~
/ |P1 | / / |P2 | /
/ +---+ / / +---+ /
/ ISP / / ISP /
/ #1 / / #2 /
~~~~~~~~~~~ ~~~~~~~~~~
| |
+-----+ +-----+
| OHT | | OHT |
| C1 | | C2 |
+--+--+ +--+--+
| |
-----+-----------------------------------
| PI
+---+--*
| HOST |
+------*
¶
HOST ------------> OHT C1 ------------> OHT P1 ---------> Server
+-----------+ +----------------+ +-----------+
| IP | data | | IP | IP | data | | IP | data |
+-----------+ +----------------+ +-----------+
src: PI src: C1 src: PI
dst: Server dst: P1 dst: Server
This document makes no request of IANA.¶
Note to RFC Editor: this section may be removed on publication as an RFC.¶
IPsec for internal packets works because internal packets are forwarded unchanged.¶
It may be listed in the future.¶