draft-ietf-idr-ix-bgp-route-server-03.txt | draft-ietf-idr-ix-bgp-route-server-04.txt | |||
---|---|---|---|---|
IDR Working Group E. Jasinska | IDR Working Group E. Jasinska | |||
Internet-Draft Microsoft Corporation | Internet-Draft Netflix, Inc | |||
Intended status: Standards Track N. Hilliard | Intended status: Standards Track N. Hilliard | |||
Expires: March 02, 2014 INEX | Expires: September 4, 2014 INEX | |||
R. Raszuk | R. Raszuk | |||
NTT MCL Inc. | NTT MCL Inc. | |||
N. Bakker | N. Bakker | |||
AMS-IX B.V. | Akamai Technologies B.V. | |||
August 29, 2013 | March 3, 2014 | |||
Internet Exchange Route Server | Internet Exchange Route Server | |||
draft-ietf-idr-ix-bgp-route-server-03 | draft-ietf-idr-ix-bgp-route-server-04 | |||
Abstract | Abstract | |||
This document outlines a specification for multilateral | This document outlines a specification for multilateral | |||
interconnections at Internet exchange points (IXPs). Multilateral | interconnections at Internet exchange points (IXPs). Multilateral | |||
interconnection is a method of exchanging routing information between | interconnection is a method of exchanging routing information between | |||
three or more exterior BGP speakers using a single intermediate | three or more exterior BGP speakers using a single intermediate | |||
broker system, referred to as a route server. Route servers are | broker system, referred to as a route server. Route servers are | |||
typically used on shared access media networks, such as Internet | typically used on shared access media networks, such as Internet | |||
exchange points (IXPs), to facilitate simplified interconnection | exchange points (IXPs), to facilitate simplified interconnection | |||
skipping to change at page 1, line 42 | skipping to change at page 1, line 42 | |||
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 http://datatracker.ietf.org/drafts/current/. | Drafts is at http://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 March 02, 2014. | This Internet-Draft will expire on September 4, 2014. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2013 IETF Trust and the persons identified as the | Copyright (c) 2014 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 | |||
(http://trustee.ietf.org/license-info) in effect on the date of | (http://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 5, line 35 | skipping to change at page 5, line 31 | |||
possible, there are circumstances where control of path distribution | possible, there are circumstances where control of path distribution | |||
on a per-client basis is important to ensure that desired | on a per-client basis is important to ensure that desired | |||
interconnection policies are met. | interconnection policies are met. | |||
The control of path distribution on a per-client basis can lead to a | The control of path distribution on a per-client basis can lead to a | |||
path being hidden from the route server client. We refer to this as | path being hidden from the route server client. We refer to this as | |||
"path hiding". | "path hiding". | |||
2.3.1. Path Hiding on a Route Server | 2.3.1. Path Hiding on a Route Server | |||
___ ___ | ___ ___ | |||
/ \ / \ | / \ / \ | |||
..| AS1 |..| AS2 |.. | ..| AS1 |..| AS2 |.. | |||
: \___/ \___/ : | : \___/ \___/ : | |||
: \ / | : | : \ / | : | |||
: \ / | : | : \ / | : | |||
: IXP \/ | : | : IXP \/ | : | |||
: /\ | : | : /\ | : | |||
: / \ | : | : / \ | : | |||
: ___/____\_|_ : | : ___/____\_|_ : | |||
: / \ / \ : | : / \ / \ : | |||
..| AS3 |..| AS4 |.. | ..| AS3 |..| AS4 |.. | |||
\___/ \___/ | \___/ \___/ | |||
Figure 1: Per-Client Policy Controlled Interconnection at an IXP | Figure 1: Per-Client Policy Controlled Interconnection at an IXP | |||
Using the example in Figure 1, AS1 does not directly exchange prefix | Using the example in Figure 1, AS1 does not directly exchange prefix | |||
information with either AS2 or AS3 at the IXP, but only interconnects | information with either AS2 or AS3 at the IXP, but only interconnects | |||
with AS4. | with AS4. | |||
In the traditional bilateral interconnection model, per-client policy | In the traditional bilateral interconnection model, per-client policy | |||
control to a third party exchange participant is accomplished either | control to a third party exchange participant is accomplished either | |||
by not engaging in a bilateral interconnection with that participant | by not engaging in a bilateral interconnection with that participant | |||
skipping to change at page 9, line 29 | skipping to change at page 9, line 29 | |||
[I-D.ietf-grow-diverse-bgp-path-dist] | [I-D.ietf-grow-diverse-bgp-path-dist] | |||
Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K. | Raszuk, R., Fernando, R., Patel, K., McPherson, D., and K. | |||
Kumaki, "Distribution of diverse BGP paths.", draft-ietf- | Kumaki, "Distribution of diverse BGP paths.", draft-ietf- | |||
grow-diverse-bgp-path-dist-08 (work in progress), July | grow-diverse-bgp-path-dist-08 (work in progress), July | |||
2012. | 2012. | |||
[I-D.ietf-idr-add-paths] | [I-D.ietf-idr-add-paths] | |||
Walton, D., Retana, A., Chen, E., and J. Scudder, | Walton, D., Retana, A., Chen, E., and J. Scudder, | |||
"Advertisement of Multiple Paths in BGP", draft-ietf-idr- | "Advertisement of Multiple Paths in BGP", draft-ietf-idr- | |||
add-paths-08 (work in progress), December 2012. | add-paths-09 (work in progress), October 2013. | |||
[RFC1863] Haskin, D., "A BGP/IDRP Route Server alternative to a full | ||||
mesh routing", RFC 1863, October 1995. | ||||
[RFC4223] Savola, P., "Reclassification of RFC 1863 to Historic", | ||||
RFC 4223, October 2005. | ||||
[RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route | [RFC4456] Bates, T., Chen, E., and R. Chandra, "BGP Route | |||
Reflection: An Alternative to Full Mesh Internal BGP | Reflection: An Alternative to Full Mesh Internal BGP | |||
(IBGP)", RFC 4456, April 2006. | (IBGP)", RFC 4456, April 2006. | |||
[RFC5226] Narten, T. and H. Alvestrand, "Guidelines for Writing an | ||||
IANA Considerations Section in RFCs", BCP 26, RFC 5226, | ||||
May 2008. | ||||
Authors' Addresses | Authors' Addresses | |||
Elisa Jasinska | ||||
Microsoft Corporation | ||||
One Microsoft Way | ||||
Redmond, WA 98052 | ||||
US | ||||
Email: ejas@microsoft.com | Elisa Jasinska | |||
Netflix, Inc | ||||
100 Winchester Circle | ||||
Los Gatos, CA 95032 | ||||
USA | ||||
Email: elisa@netflix.com | ||||
Nick Hilliard | Nick Hilliard | |||
INEX | INEX | |||
4027 Kingswood Road | 4027 Kingswood Road | |||
Dublin 24 | Dublin 24 | |||
IE | IE | |||
Email: nick@inex.ie | Email: nick@inex.ie | |||
Robert Raszuk | Robert Raszuk | |||
NTT MCL Inc. | NTT MCL Inc. | |||
101 S Ellsworth Avenue Suite 350 | 101 S Ellsworth Avenue Suite 350 | |||
San Mateo, CA 94401 | San Mateo, CA 94401 | |||
US | US | |||
Email: robert@raszuk.net | Email: robert@raszuk.net | |||
Niels Bakker | Niels Bakker | |||
AMS-IX B.V. | Akamai Technologies B.V. | |||
Westeinde 12 | Kingsfordweg 151 | |||
Amsterdam, NH 1017 ZN | Amsterdam 1043 GR | |||
NL | NL | |||
Email: niels.bakker@ams-ix.net | Email: nbakker@akamai.com | |||
End of changes. 14 change blocks. | ||||
40 lines changed or deleted | 30 lines changed or added | |||
This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/ |