draft-ietf-lisp-deployment-08.txt | draft-ietf-lisp-deployment-09.txt | |||
---|---|---|---|---|
Network Working Group L. Jakab | Network Working Group L. Jakab | |||
Internet-Draft Cisco Systems | Internet-Draft Cisco Systems | |||
Intended status: Informational A. Cabellos-Aparicio | Intended status: Informational A. Cabellos-Aparicio | |||
Expires: December 28, 2013 F. Coras | Expires: January 10, 2014 F. Coras | |||
J. Domingo-Pascual | J. Domingo-Pascual | |||
Technical University of | Technical University of | |||
Catalonia | Catalonia | |||
D. Lewis | D. Lewis | |||
Cisco Systems | Cisco Systems | |||
June 26, 2013 | July 9, 2013 | |||
LISP Network Element Deployment Considerations | LISP Network Element Deployment Considerations | |||
draft-ietf-lisp-deployment-08.txt | draft-ietf-lisp-deployment-09.txt | |||
Abstract | Abstract | |||
This document discusses the different scenarios for the deployment of | This document discusses the different scenarios for the deployment of | |||
the new network elements introduced by the Locator/Identifier | the new network elements introduced by the Locator/Identifier | |||
Separation Protocol (LISP). | Separation Protocol (LISP). | |||
Status of this Memo | Status of this Memo | |||
This Internet-Draft is submitted in full conformance with the | This Internet-Draft is submitted in full conformance with the | |||
skipping to change at page 1, line 38 | skipping to change at page 1, line 38 | |||
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 December 28, 2013. | This Internet-Draft will expire on January 10, 2014. | |||
Copyright Notice | Copyright Notice | |||
Copyright (c) 2013 IETF Trust and the persons identified as the | Copyright (c) 2013 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 | |||
skipping to change at page 8, line 27 | skipping to change at page 8, line 27 | |||
encapsulated packets. | encapsulated packets. | |||
o In this scenario, each ITR is serving fewer hosts than in the case | o In this scenario, each ITR is serving fewer hosts than in the case | |||
when it is deployed at the border of the network. It has been | when it is deployed at the border of the network. It has been | |||
shown that cache hit ratio grows logarithmically with the amount | shown that cache hit ratio grows logarithmically with the amount | |||
of users [cache]. Taking this into account, when ITRs are | of users [cache]. Taking this into account, when ITRs are | |||
deployed closer to the host the effectiveness of the mapping cache | deployed closer to the host the effectiveness of the mapping cache | |||
may be lower (i.e., the miss ratio is higher). Another | may be lower (i.e., the miss ratio is higher). Another | |||
consequence of this is that the site may transmit a higher amount | consequence of this is that the site may transmit a higher amount | |||
of Map-Requests, increasing the load on the distributed mapping | of Map-Requests, increasing the load on the distributed mapping | |||
database. To lower the impact, the site could use a local caching | database. | |||
Map Resolver. | ||||
o By placing the ITRs inside the site, they will still need global | o By placing the ITRs inside the site, they will still need global | |||
RLOCs, and this may add complexity to intra-site routing | RLOCs, and this may add complexity to intra-site routing | |||
configuration, and further intra-site issues when there is a | configuration, and further intra-site issues when there is a | |||
change of providers. | change of providers. | |||
2.4. Inter-Service Provider Traffic Engineering | 2.4. Inter-Service Provider Traffic Engineering | |||
At the time of this writing, if two ISPs want to control their | At the time of this writing, if two ISPs want to control their | |||
ingress TE policies for transit traffic between them, they need to | ingress TE policies for transit traffic between them, they need to | |||
End of changes. 5 change blocks. | ||||
6 lines changed or deleted | 5 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/ |