At IETF 94, v6ops advised the routing ADs and Routing Working Group that PA multihoming would not work without a source/destination routing solution. This draft was developed in response.
> Begin forwarded message: > > From: <[email protected]> > Subject: New Version Notification for > draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt > Date: July 5, 2016 at 5:58:25 PM PDT > To: Chris Bowers <[email protected]>, Jen Linkova <[email protected]>, "Fred > Baker" <[email protected]>, "J. Linkova" <[email protected]> > > > A new version of I-D, draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt > has been successfully submitted by Fred Baker and posted to the > IETF repository. > > Name: draft-bowbakova-rtgwg-enterprise-pa-multihoming > Revision: 00 > Title: Enterprise Multihoming using Provider-Assigned > Addresses without Network Prefix Translation: Requirements and Solution > Document date: 2016-07-05 > Group: Individual Submission > Pages: 44 > URL: > https://www.ietf.org/internet-drafts/draft-bowbakova-rtgwg-enterprise-pa-multihoming-00.txt > Status: > https://datatracker.ietf.org/doc/draft-bowbakova-rtgwg-enterprise-pa-multihoming/ > Htmlized: > https://tools.ietf.org/html/draft-bowbakova-rtgwg-enterprise-pa-multihoming-00 > > > Abstract: > Connecting an enterprise site to multiple ISPs using provider- > assigned addresses is difficult without the use of some form of > Network Address Translation (NAT). Much has been written on this > topic over the last 10 to 15 years, but it still remains a problem > without a clearly defined or widely implemented solution. Any > multihoming solution without NAT requires hosts at the site to have > addresses from each ISP and to select the egress ISP by selecting a > source address for outgoing packets. It also requires routers at the > site to take into account those source addresses when forwarding > packets out towards the ISPs. > > This document attempts to define a complete solution to this problem. > It covers the behavior of routers to forward traffic taking into > account source address, and it covers the behavior of host to select > appropriate source addresses. It also covers any possible role that > routers might play in providing information to hosts to help them > select appropriate source addresses. In the process of exploring > potential solutions, this documents also makes explicit requirements > for how the solution would be expected to behave from the perspective > of an enterprise site network administrator . > > > > > Please note that it may take a couple of minutes from the time of submission > until the htmlized version and diff are available at tools.ietf.org. > > The IETF Secretariat >
signature.asc
Description: Message signed with OpenPGP using GPGMail
_______________________________________________ rtgwg mailing list [email protected] https://www.ietf.org/mailman/listinfo/rtgwg
