Ivip4 ETR Address Forwarding
draft-whittle-ivip-etr-addr-forw-01
| Document | Type |
Expired Internet-Draft
(individual)
Expired & archived
|
|
|---|---|---|---|
| Author | Robin Whittle | ||
| Last updated | 2010-07-08 | ||
| RFC stream | (None) | ||
| Intended RFC status | (None) | ||
| Formats | |||
| Stream | Stream state | (No stream defined) | |
| Consensus boilerplate | Unknown | ||
| RFC Editor Note | (None) | ||
| IESG | IESG state | Expired | |
| Telechat date | (None) | ||
| Responsible AD | (None) | ||
| Send notices to | (None) |
This Internet-Draft is no longer active. A copy of the expired Internet-Draft is available in these formats:
Abstract
ETR Address Forwarding (EAF) is a novel method by which an IPv4 Core- Edge Separation solution to the Internet's routing scaling problem can tunnel packets from an ITR to an ETR. EAF involves using 31 bits of the IPv4 header for new purposes: bit 48, the More Fragments flag, the Fragment Offset field and the Header Checksum field - to carry a 30 bit ETR address. Consequently, packets in this format need to be handled by routers with upgraded functionality. EAF is an alternative to encapsulation and has advantages including: simpler ITRs and ETRs, direct support for conventional RFC 1191 PMTUD, no encapsulation overhead and full compatibility with IPsec AH and Traceroute. This I-D also briefly explores an alternative to this approach: a new header, of the same length and different, with a different 4 bit Version, to carry 31 bits of ETR address.
Authors
(Note: The e-mail addresses provided for the authors of this Internet-Draft may no longer be valid.)