idnits 2.17.1 draft-previdi-cdni-footprint-advertisement-02.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 26 instances of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (September 19, 2012) is 4237 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Outdated reference: A later version (-17) exists of draft-ietf-cdni-requirements-03 Summary: 0 errors (**), 0 flaws (~~), 3 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 CDNI WG S. Previdi, Ed. 3 Internet-Draft F. Le Faucheur 4 Intended status: Standards Track J. Medved 5 Expires: March 23, 2013 Cisco Systems, Inc. 6 A. Guillou 7 SFR 8 September 19, 2012 10 CDNI Footprint Advertisement 11 draft-previdi-cdni-footprint-advertisement-02 13 Abstract 15 This document describes the use of BGP for Content Delivery Networks 16 (CDNs) in order to advertise information about footprint and 17 connectivity to footprint in the context of CDNI. 19 Requirements Language 21 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 22 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 23 document are to be interpreted as described in RFC 2119 [RFC2119]. 25 Status of this Memo 27 This Internet-Draft is submitted in full conformance with the 28 provisions of BCP 78 and BCP 79. 30 Internet-Drafts are working documents of the Internet Engineering 31 Task Force (IETF). Note that other groups may also distribute 32 working documents as Internet-Drafts. The list of current Internet- 33 Drafts is at http://datatracker.ietf.org/drafts/current/. 35 Internet-Drafts are draft documents valid for a maximum of six months 36 and may be updated, replaced, or obsoleted by other documents at any 37 time. It is inappropriate to use Internet-Drafts as reference 38 material or to cite them other than as "work in progress." 40 This Internet-Draft will expire on March 23, 2013. 42 Copyright Notice 44 Copyright (c) 2012 IETF Trust and the persons identified as the 45 document authors. All rights reserved. 47 This document is subject to BCP 78 and the IETF Trust's Legal 48 Provisions Relating to IETF Documents 49 (http://trustee.ietf.org/license-info) in effect on the date of 50 publication of this document. Please review these documents 51 carefully, as they describe your rights and restrictions with respect 52 to this document. Code Components extracted from this document must 53 include Simplified BSD License text as described in Section 4.e of 54 the Trust Legal Provisions and are provided without warranty as 55 described in the Simplified BSD License. 57 Table of Contents 59 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . . 4 60 2. Terminology . . . . . . . . . . . . . . . . . . . . . . . . . 4 61 3. CDNI Mesh and MP-BGP . . . . . . . . . . . . . . . . . . . . . 5 62 4. CDNI Information . . . . . . . . . . . . . . . . . . . . . . . 6 63 4.1. Footprint . . . . . . . . . . . . . . . . . . . . . . . . 6 64 4.2. Footprint Elements (FPE) . . . . . . . . . . . . . . . . . 6 65 4.3. Footprint Reachability (FPR) . . . . . . . . . . . . . . . 7 66 4.4. CDN Capability Information (CAP) . . . . . . . . . . . . . 7 67 5. CDNI Functional Components . . . . . . . . . . . . . . . . . . 8 68 5.1. CDNI Databases . . . . . . . . . . . . . . . . . . . . . . 8 69 5.1.1. CDNI Footprint Elements Database . . . . . . . . . . . 8 70 5.1.2. CDNI Footprint Reachability Database . . . . . . . . . 9 71 5.1.3. CDNI Capability Database . . . . . . . . . . . . . . . 9 72 5.2. CDNI MP-BGP Messages . . . . . . . . . . . . . . . . . . . 9 73 5.2.1. CDNI MP-BGP Footprint Element Advertisement . . . . . 9 74 5.2.2. CDNI MP-BGP Footprint Reachability Advertisement . . . 10 75 5.2.3. CDNI Capability Advertisement . . . . . . . . . . . . 10 76 5.3. CDNI Information Elements (Attributes) . . . . . . . . . . 10 77 5.3.1. CDN Identifier . . . . . . . . . . . . . . . . . . . . 10 78 5.3.2. Footprint Element Identifier . . . . . . . . . . . . . 10 79 5.3.3. Reachable Footprint Element . . . . . . . . . . . . . 11 80 5.3.4. Origin_AS_PATH . . . . . . . . . . . . . . . . . . . . 11 81 5.3.5. CDN Capabilities . . . . . . . . . . . . . . . . . . . 11 82 5.4. CDNI MP-BGP NLRIs . . . . . . . . . . . . . . . . . . . . 11 83 6. CDNI Example . . . . . . . . . . . . . . . . . . . . . . . . . 12 84 6.1. Topology . . . . . . . . . . . . . . . . . . . . . . . . . 12 85 6.2. CDN2 Footprint Element Advertisements . . . . . . . . . . 12 86 6.3. Footprint Element Database in each CDN . . . . . . . . . . 13 87 6.4. Footprint Reachability Advertisements . . . . . . . . . . 14 88 6.5. Capability Advertisements . . . . . . . . . . . . . . . . 16 89 6.6. FPE, FPR and CAP Databases in uCDN . . . . . . . . . . . . 16 90 6.7. Request Routing for user 2.2.2.2 . . . . . . . . . . . . . 17 91 6.8. Request Routing for user 1.1.1.1 . . . . . . . . . . . . . 18 92 7. CDNI MP-BGP Encodings . . . . . . . . . . . . . . . . . . . . 19 93 7.1. CDNI Attributes . . . . . . . . . . . . . . . . . . . . . 19 94 7.1.1. CDNI Identifier . . . . . . . . . . . . . . . . . . . 19 95 7.1.2. FPE Identifier . . . . . . . . . . . . . . . . . . . . 19 96 7.1.3. Origin_AS_PATH . . . . . . . . . . . . . . . . . . . . 19 97 7.1.4. Capabilities . . . . . . . . . . . . . . . . . . . . . 20 98 7.2. CDNI Messages . . . . . . . . . . . . . . . . . . . . . . 20 99 7.2.1. FPE Advertisement . . . . . . . . . . . . . . . . . . 20 100 7.2.2. FPR Advertisement . . . . . . . . . . . . . . . . . . 21 101 7.2.3. CAP Advertisement . . . . . . . . . . . . . . . . . . 21 102 7.3. CDNI NLRI . . . . . . . . . . . . . . . . . . . . . . . . 22 103 7.3.1. CDNI-NLRI Type 1: FPE Advertisement . . . . . . . . . 22 104 7.3.2. CDNI-NLRI Type 2: FPR Advertisement . . . . . . . . . 23 105 7.3.3. CDNI-NLRI Type 3: CAP Advertisement . . . . . . . . . 23 106 7.3.4. NLRI Encoding . . . . . . . . . . . . . . . . . . . . 24 107 8. Compliance with CDNI Requirements . . . . . . . . . . . . . . 25 108 9. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 25 109 10. Security Considerations . . . . . . . . . . . . . . . . . . . 25 110 11. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . 25 111 12. References . . . . . . . . . . . . . . . . . . . . . . . . . . 25 112 12.1. Normative References . . . . . . . . . . . . . . . . . . . 25 113 12.2. Informative References . . . . . . . . . . . . . . . . . . 26 114 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . . 26 116 1. Introduction 118 The IETF CDN Interconnection (CDNI) Working Group is chartered to 119 develop specifications for interconnecting standalone CDNs so that 120 their collective CDN footprint can be leveraged for the end-to-end 121 delivery of content from Content Service Providers (CSPs) to End 122 Users. 124 [I-D.jenkins-cdni-problem-statement] outlines the problem area that 125 the CDNI working group is chartered to address. 126 [I-D.bertrand-cdni-use-cases] discusses the use cases for CDN 127 Interconnection and [I-D.davie-cdni-framework] discusses the 128 technology framework for the CDNI solution and interfaces. 130 When an upstream CDN (uCDN) receives a request from a user, it has to 131 determine what is the downstream CDN (dCDN) to which the request is 132 to be redirected. This CDN selection decision can take into account 133 various criteria such as administrative preferences (for example 134 based on the commercial arrangements between the uCDN and candidate 135 dCDNs including associated request handling costs) and/or such as 136 whether candidate CDNs are have caches that are topologically close 137 to the user and capable of handling that request. Therefore, as 138 discussed in section "Dynamic Footprint Discovery" of 139 [I-D.davie-cdni-framework], there are situations where being able to 140 dynamically discover the set of requests that a given dCDN is willing 141 and able to serve is beneficial. As also discussed in 142 [I-D.davie-cdni-framework], this information could be potentially 143 provided by the dCDN in response to a query by the uCDN, or the 144 information (or its changes) could be spontaneously advertised by the 145 dCDN. 147 The proposal outlined in this document makes use of Multiprotocol-BGP 148 (MP-BGP [RFC4760]) in order for CDNs and/or ISPs to advertise their 149 footprint information as well as for CDNs to advertise their 150 connectivity to these footprints. In addition CDNs use MP-BGP 151 advertisements to represent their interconnectivity. 153 2. Terminology 155 The following terminology is used in this document: 157 CDNI Mesh: the set of CDNs participating into CDNI and using MP- 158 BGP sessions between them in accordance with the approach defined 159 in this document. A CDNI Mesh has no requirements in terms of 160 topology, i.e.: the mesh can be partial, full or hierarchical. 162 Footprint (FP): The exhaustive set of Prefixes a CDN is willing to 163 serve. 165 Footprint Element (FPE): Arbitrary set of prefixes with 166 attributes. They can be implicit (inferred from BGP) or explicit 167 (advertised). 169 Implicit Footprint Element Advertisement (FPE Implicit 170 Advertisement): Footprint Element information derived from the BGP 171 database. 173 Footprint Element Advertisement (FPE-Adv): MP-BGP Message used by 174 a CDN in order to advertise or withdrawn Footprint Elements and 175 their attributes. 177 Footprint Reachability Advertisement (FPR-Adv): MP-BGP Message 178 used by a CDN in order to advertise or withdrawn Footprint 179 reachability information. 181 Capability Advertisement (CAP-Adv): MP-BGP Message used by a CDN 182 in order to advertise or withdrawn capability information. 184 3. CDNI Mesh and MP-BGP 186 CDNI enables CDNs to communicate in order to deliver content in a 187 collaborative mode. 189 CDNI Mesh will make use of Multiprotocol-BGP (MP-BGP [RFC4760]) for 190 the exchange of footprint, reachability and capability information. 192 We define a new Sub Address Family (CDNI-SAFI, TBD) for Address 193 Families (AF) 1 (IPv4) and 2 (IPv6) and a set of new Network Layer 194 Reachability Information (NLRI) that will carry either FPE, FPR or 195 CAP advertisements. The NLRI will have a NLRI type determining the 196 content (i.e.: FPE, FPR or CAP) so to distinguish advertisements. 198 The advantage of using a separate address family is to isolate CDNI 199 information from regular BGP-4 Internet information so to not 200 compromise in any way the security and reliability of the current BGP 201 information exchange used for IP network layer routing. 203 The advantage of having separate FPE, FPR and CAP information is that 204 a CDN needs not originate (and update) FPE information each time 205 there's a change in the way a CDN is connected to other CDNs. E.g.: 206 if the complete Footprint information was to be exchanged between 207 CDNs, it would consist of a very large amount of prefixes advertised 208 (and re-advertised) each time a CDNI interconnection changes in the 209 CDNI Mesh. 211 When an existing CDNI connection is removed or when a new connection 212 between two CDNs is established, the only advertisements that need to 213 be updated are the ones concerning the FPR. 215 While footprint information is expected to be relatively stable, the 216 CDNI Mesh (i.e.: the connectivity between CDNs) and the reachability 217 from CDN to footprints may be impacted by network events. Also, the 218 connectivity between CDNs may be affected by the CDN selection policy 219 which may be modified relatively frequently. 221 CDNI FPR advertisements allow the CDNI Mesh to scale by adapting 222 easily to topology changes. In fact, just a few number of FPR 223 advertisements are used by each CDN which makes the CDNI MP-BGP 224 scheme very scalable. 226 4. CDNI Information 228 CDNI Information includes: 230 Footprint (FP). 232 Footprint Element (FPE). 234 Footprint Reachability (FPR). 236 CDN Capabilities (CAP). 238 4.1. Footprint 240 Footprint represents the exhaustive set of prefixes a CDN is willing 241 to serve. The set of prefixes may belong to one or more Autonomous 242 Systems or may include subset of prefixes of one or more Autonomous 243 Systems. In other words, there is no strict relationship between an 244 Autonomous System and the CDN Footprint. 246 Example: if CDN-A delivers content to ISP-A users, then CDN-A 247 footprint consists of all prefixes owned and connected to ISP-A. 249 4.2. Footprint Elements (FPE) 251 Footprint Elements refers to an arbitrary set of prefixes part of a 252 CDN Footprint. 254 FPEs can be inferred from the BGP-4 Internet database. It is assumed 255 that the CDN will have a BGP-4 feed with Internet prefixes that are 256 necessary in order for the CDNI Mesh to operate and from which it 257 will be able to derive FPEs. 259 The CDN will maintain a FPE Database that is isolated from the 260 regular BGP Internet database. The CDNI FPE database uses the CDNI- 261 SAFI (TBD) MP-BGP address family. 263 FPEs can be implicit (inferred from BGP) or explicit (advertised). 265 Example 1: if CDN-A is willing to serve Autonomous System A and 266 Autonomous System B users, then two footprints elements will be 267 inferred from the BGP database in all CDNs: FPE-ASA and FPE-ASB. 268 Then, CDN-A will advertise its reachability to FPEs FPE-ASA and FPE- 269 ASB. In this example FPEs are inferred by all CDNs by just looking 270 at the BGP-4 Internet Database. 272 Example 2: if CDN-B is willing to serve Autonomous System A users and 273 a subset of Autonomous System B users, then CDN-B Footprint consist 274 of two FPEs: Autonomous System A and the set of prefixes representing 275 the subset of Autonomous System B users. Autonomous System 'A' FPE 276 is inferred from BGP-4 Database while the subset of Autonomous System 277 B users is an FPE that will be explicitly advertised by CDN-B to the 278 CDNI Mesh. 280 The CDNI FPE Database includes FPEs inferred from the BGP-4 281 (Internet) database as well as FPE Advertisements originated by the 282 CDN and/or received from other CDNI Mesh members. 284 4.3. Footprint Reachability (FPR) 286 Footprint Reachability refers to the way a CDN can reach to one or 287 more FPEs. FPR consists of advertisements originated by each CDN for 288 each of its FPE and advertised to the CDNI Mesh (through MP-BGP 289 Messages). 291 FPR Information is stored in the CDNI FPR Database which contains the 292 information originated by the CDN and the information received from 293 the other CDNs in the CDNI Mesh. 295 4.4. CDN Capability Information (CAP) 297 Each CDN advertises to the CDNI Mesh the set of its capabilities. 298 The CDN originates a CDN Capabilities message (CAP) message 299 containing the attributes describing such capabilities. 301 Each CDN MUST originate a Capabilities message and each CDN will 302 store in the CDNI Capabilities Database the set of Capabilities 303 messages received from other members of the CDNI Mesh. 305 5. CDNI Functional Components 307 This section describes the CDNI functional components (databases, 308 messages, information sets) stored and exchanged between CDNs and 309 related to CDN Footprints and Capabilities. This document proposes 310 the use of Multiprotocol-BGP for exchanging the CDNI information. 311 The details of MP-BGP encodings are described in Section 7. 313 5.1. CDNI Databases 315 This section describes the set of databases defined for the 316 propagation of Fooptrint and Capability information across the CDNI 317 Mesh. The goal of this section is to explain the different 318 information elements that are required in order to properly determine 319 FPE, FPR and CAP information. This section is not to be intended as 320 an implenentation description. An implementation may combine or 321 merge all data into single or multiple databases. 323 CDNI Footprint Elements Database contains FPEs that are either 324 derived from BGP-4 Internet table or received from other CDN 325 through CDNI Footprint Elements Advertisements. 327 CDNI Footprint Reachability Database contains the advertisements 328 originated by the CDN and received from other CDNs and that 329 describe how each CDN can reach its Footprint Elements. 331 CDNI Capability Database contains the set of CDN capabilities 332 advertised by each CDN. 334 5.1.1. CDNI Footprint Elements Database 336 FPE Database contains the FPEs that a CDN has inferred from the BGP-4 337 Internet database as well as FPEs that have been explicitly 338 advertised by other CDNs. 340 FPE Database includes prefixes and their attributes as known in the 341 BGP-4 Internet Database (e.g.: prefix, AS_PATH, MED, Communities, 342 etc) in addition to CDNI specific attributes that are defined in 343 following sections. 345 FPE Database also contains the FPEs that have been explicitly 346 advertised by remote CDNs. 348 It is expected that for most of CDNs, the majority of the FPE 349 information is inferred from BGP-4 Internet Database so to reduce 350 significantly the advertisement of FPEs. 352 5.1.2. CDNI Footprint Reachability Database 354 FPR Database contains the set of FPEs each CDN claimed reachability 355 to. This includes: 357 The set of FPEs this CDN can reach. 359 The set of FPEs other CDNs have advertised their reachability to. 361 The FPR Database is populated by the FPR Advertisement messages 362 originated and sent by each CDN participating into the CDNI Mesh. 364 5.1.3. CDNI Capability Database 366 Capability (CAP) Database contains the set of capabilities advertised 367 by each CDN. 369 The CAP Database is populated by the CAP Advertisement messages 370 originated and sent by each CDN participating into the CDNI Mesh. 372 5.2. CDNI MP-BGP Messages 374 We define three new MP-BGP messages for the advertisement of CDNI 375 Address Familiy NLRIs: 377 Footprint Element Advertisement (FPE Advertisement) describing an 378 FPEs and its attributes. 380 Footprint Reachability Advertisement (FPR Advertisement) 381 describing how a CDN can reach one or more FPEs. 383 Capability Advertisement (CAP Advertisement) describing CDN 384 capabilities. 386 The propagation of CDNI Messages throughout the CDNI Mesh is done 387 according to standard BGP rules and the inter-CDN connectivity will 388 be reflected in the BGP attributes, e.g.: AS_PATH will describe the 389 different CDNs the advertisement traversed during its propagation in 390 the CDNI Mesh thus describing the inter-CDN connectivity. 392 5.2.1. CDNI MP-BGP Footprint Element Advertisement 394 FPE Advertisement is originated by a CDN willing to group prefixes it 395 can reach under a unique identifier (identifying the FPE). The 396 message is originated and sent out by the CDN and propagated 397 throughout the CDNI Mesh according to MP-BGP propagation rules. 399 The FPE Advertisement includes CDNI NLRI, representing the FPE 400 address space, and attributes among which the identifier of the FPE. 402 5.2.2. CDNI MP-BGP Footprint Reachability Advertisement 404 In the CDNI Mesh, each CDN MUST advertise the different Footprint 405 Elements it reaches. The CDN maintains a FPE Reachability Database 406 with entries describing its connectivity to Footprints Elements. 408 The propagation of CDN Connectivity advertisements throughout the 409 CDNI Mesh is done according to standard BGP rules and the inter-CDN 410 connectivity will be reflected in the BGP attributes (e.g.: AS_PATH 411 will describe the different CDNs the advertisement traversed during 412 its propagation in the CDNI Mesh thus describing the inter-CDN 413 connectivity). 415 5.2.3. CDNI Capability Advertisement 417 Each CDN MUST advertise information describing its capabilities. 418 This is done in the CAP dvertisement message. 420 5.3. CDNI Information Elements (Attributes) 422 This section describes the different information elements contained 423 in the CDNI Databases. 425 5.3.1. CDN Identifier 427 CDN_Identifier uniquely identifies the CDN within the CDNI Mesh. CDN 428 Identifier is exchanged inside the CDNI (MP-BGP) messages between 429 CDNs. 431 5.3.2. Footprint Element Identifier 433 The role of the Footprint Element Identifier is to group all prefixes 434 part of the same FPE under a unique identifier. This allows a CDN to 435 claim reachability to the FPE by just specifying the FPE Identifier 436 rather than each individual prefix of the footprint. 438 When inferring the CDNI footprint information from the regular BGP-4 439 Internet database, the FPE Identifier is derived from the first ASN 440 in the AS_PATH of the prefix, i.e.: the AS of origin of the prefix. 442 FPE Identifiers are present in both FPE Advertisement and FPR 443 Advertisement. In the FPE Advertisement it is used to arbitrarily 444 group prefixes under the same Identifier while in the FPR 445 Advertisement, the FPE Identifier is used in order to describe which 446 FPEs a CDN can reach. 448 5.3.3. Reachable Footprint Element 450 Reachable FPE contains the FPE Identifier of each FPE the CDN claim 451 reachability to. Multiple instances of Reachable FPE are allowed in 452 the same FPR Advertisement message. FPE Identifier is assigned to 453 the FPE by the CDN advertising the FPE (in the FPE Advertisement 454 Message). FPE Identifier contains an AS number when the FPE has been 455 inferred from the BGP database. 457 5.3.4. Origin_AS_PATH 459 This attribute contains the prefix AS_PATH value that is present in 460 the BGP-4 Internet Database of the CDN originating the FPR 461 advertisement. 463 Origin_AS_PATH aims to describe how the CDN can reach a given FPE and 464 is present only in FPR advertisements. 466 5.3.5. CDN Capabilities 468 Capabilities are expressed in a set of attributes the CDN inserts in 469 the Capability Advertisement message. 471 5.4. CDNI MP-BGP NLRIs 473 We define three types of CDNI NLRI: FPE-NLRI, FPR-NLRI and CAP-NLRI 475 When referred to FPE, the NLRI contains either an IPv4 or IPv6 476 prefix. 478 In some cases, a given FPE prefix is reachable by multiple CDNs. MP- 479 BGP, according to BGP selection rule, will allow to select only one 480 FPE and therefore information about FPE being multi-reachability 481 through different CDNs may be lost. In order to prevent this, the 482 CDNI NLRI contains a CDNI FPE Distinguisher so to make two identical 483 prefixes different from a BGP selection perspective. The behavior is 484 similar to what defined in [RFC4364]. 486 FPR NLRI consists of one or more FPE-Identifiers representing the 487 FPEs the CDN can reach. 489 CAP-NLRI contains a IPv4 or IPv6 prefix (called the CAP-Prefix) 490 beloning to the CDN address space originating the CAP Advertisement 491 Message. Capabilities will be avertised using attributes to the CAP- 492 prefix. 494 6. CDNI Example 496 This section illustrates an example of CDNI Mesh with the set of 497 databases and messages that are exchanged between CDNs. 499 6.1. Topology 501 The following topology is used: 502 CDN2 CDN3 uCDN 503 1.1.1.0/24 |--AS100---AS200---AS300---AS400---Internet---AS500 504 2.2.2.0/24 | |-----------------| | 505 3.3.3.0/24 | | 506 |------------------------| 508 CDN2, CDN3 and uCDN participate into the CDNI Mesh. 510 CDNI Mesh includes following MP-BGP Sessions: CDN2-CDN3 and CDN3- 511 uCDN. Note that there's no MP-BGP session between CDN2 and uCDN. 513 AS100 and AS400 have no CDN. 515 AS100 advertises all prefixes to AS300 and AS400. 517 AS100 advertises only prefix 1.1.1.0/24 and 3.3.3.0/24 to AS200. 519 6.2. CDN2 Footprint Element Advertisements 521 CDN2 originates following Footprint Elements Advertisements: 523 Prefix CDN2:1.1.1.0/24 524 AS_PATH: {CDN2} 525 Footprint-Element Identifier: FP-CDN2 527 Prefix CDN2:3.3.3.0/24 528 AS_PATH: {CDN2} 529 Footprint-Element Identifier: FP-CDN2 531 where: 533 Prefix CDN2:1.1.1.0/24 and Prefix CDN2:3.3.3.0/24 are the 534 two prefixes advertised with the CDNI FPE Distinguisher 535 corresponding to CDN2. The CDNI FPE Distinguisher is 536 required so to distinguish between possible identical 537 prefixes advertised by other CDNs. 539 AS_PATH contains the set of CDNs the update has traversed. 540 It is mainly used for loop prevention in BGP in the CDNI 541 Mesh. 543 Note: the AS numbers in the AS_PATH represent the CDNs, 544 not the BGP autonomous systems. 546 Footprint-Element Identifier contains the identifier of 547 the Footprint-Element and it is used by CDN2 when 548 originating the Footprint Reachability Advertisement. 550 Note that uCDN and CDN3 do NOT originate any Footprint Element 551 Message. 553 6.3. Footprint Element Database in each CDN 555 Footprint Elements Database in constructed by inferring all info from 556 BGP database plus the Footprint Elements Advertisements received from 557 within the CDNI Mesh. 559 In CDN2 the Footprint Elements Database is as follows: 560 1.1.1.0/24; AS_PATH: {100} ===\ 561 2.2.2.0/24; AS_PATH: {300, 100} ====> inferred from 562 3.3.3.0/24; AS_PATH: {100} ===/ BGP table 564 CDN2:1.1.1.0/24 565 AS_PATH: {} 566 Footprint-Element Identifier: FP-CDN2 568 CDN2:3.3.3.0/24 569 AS_PATH: {} 570 Footprint-Element Identifier: FP-CDN2 572 In CDN3 the Footprint Elements Database is as follows: 573 1.1.1.0/24; AS_PATH: {100} ===\ 574 2.2.2.0/24; AS_PATH: {100} ====> inferred from 575 3.3.3.0/24; AS_PATH: {100} ===/ BGP table 577 CDN2:1.1.1.0/24 578 AS_PATH: {CDN2} 579 Footprint-Elements Identifier: FP-CDN2 581 CDN2:3.3.3.0/24 582 AS_PATH: {CDN2} 583 Footprint-Element Identifier: FP-CDN2 585 In uCDN the Footprint Elements Database is as follows: 586 1.1.1.0/24; AS_PATH: {, 400, 100} ===\ inferred 587 2.2.2.0/24; AS_PATH: {, 400, 100} ====> from 588 3.3.3.0/24; AS_PATH: {, 400, 100} ===/ BGP table 590 CDN2:1.1.1.0/24 591 AS_PATH: {CDN3, CDN2} 592 Footprint-Element Identifier: FP-CDN2 594 CDN2:3.3.3.0/24 595 AS_PATH: {CDN3, CDN2} 596 Footprint-Element Identifier: FP-CDN2 598 The Footprint-Elements Database contains prefixes inferred from the 599 BGP database and the prefixes received through Footprint-Element 600 Advertisements. 602 Footprint-Element prefixes derived from BGP database do not require a 603 CDNI FPE Distinguisher.The way an implementation stores inferred FPE 604 information (with or without CDNI FPE Distinguisher is out of the 605 scope of this document. 607 The prefixes received by FPE Advertisements need a CDNI FPE 608 Distinguisher because multiple CDNs may advertise the same set of 609 prefixes and we need to preserve all from selection rules. 611 6.4. Footprint Reachability Advertisements 613 Each CDN will advertise its reachability to Footprint Elements: 615 CDN2 Footprint Reachability Advertisement: 617 CDN-Identifier: CDN2 618 AS_PATH: 622 Reachable Footprint-Element: AS200 623 Origin_AS_PATH: {} 625 Reachable Footprint-Element: FP-CDN2 626 Origin_AS_PATH: {100} 628 Where: 630 Origin_AS_PATH describes the BGP AS_PATHs as known in CDN2. 632 CDN2 advertises reachability to two sets of prefixes: one consists of 633 all prefixes in AS200 and another set consists of prefixes he 634 received from AS100 (and that he previously sent with Footprint- 635 Element Advertisements). 637 CDN3 Footprint Reachability Advertisement: 638 CDN-Identifier: CDN3 639 AS_PATH: 643 Reachable Footprint-Element: AS300 644 Origin_AS_PATH: {} 646 Reachable Footprint-Element: AS100 647 Origin_AS_PATH: {200, 100} 649 Where: 651 Origin_AS_PATH describes the BGP AS_PATHs as known in CDN3. 653 CDN3 advertises reachability to two sets of prefixes: AS100 and 654 AS300. 656 Each CDN advertises: 658 CDNI Identifier. 660 Set of reachable Footprint-Elements (i.e.: a set of FPE 661 Identifiers) with their corresponding Origin_AS_PATH. 663 The AS_PATH representing the BGP connectivity within the CDNI 664 Mesh. 666 6.5. Capability Advertisements 668 Each CDN originates a CAP Advertisement messages carrying information 669 about its capabilities. Each CDN will advertise: 671 A prefix owned by the CDN (i.e.: part of the CDN address space). 673 Its CDN Identifier. 675 A set of attributes describing the CDN capabilities (encoded as 676 BGP Extended Community Attributes). 678 CDN2 Capability Advertisement: 679 CDN-Identifier: CDN2 680 Communities (std/ext): representing CDN2 capabilities 681 AS_PATH: 684 NLRI: CDN2-Prefix 686 CDN3 Capability Advertisement: 687 CDN-Identifier: CDN3 688 Communities (std/ext): representing CDN capabilities 689 AS_PATH: 692 NLRI: CDN3-Prefix 694 6.6. FPE, FPR and CAP Databases in uCDN 696 uCDN has the two following databases: 698 Footprint-Elements Database: 699 1.1.1.0/24 700 AS_PATH: {, 400, 100} ==\ 701 2.2.2.0/24 ===\ 702 AS_PATH: {, 400, 100} ====> inferred from 703 3.3.3.0/24 ===/ BGP table 704 AS_PATH: {, 400, 100} ==/ 706 CDN2:1.1.1.0/24 707 AS_PATH: {CDN3, CDN2} 708 Footprint-Element Identifier: FP-CDN2 709 CDN2:3.3.3.0/24 710 AS_PATH: {CDN3, CDN2} 711 Footprint-Element Identifier: FP-CDN2 713 Footprint-Reachability Database: 714 CDN-Identifier: CDN2 715 AS-PATH: {300, 200} 717 Reachable Footprint-Element: AS200 718 Origin_AS_PATH: {} 720 Reachable Footprint-Element: FP-CDN2 721 Origin_AS_PATH: {100} 723 CDN-Identifier: CDN3 724 AS-PATH: {300} 726 Reachable Footprint-Element: AS300 727 Origin_AS_PATH: {} 729 Reachable Footprint-Element: AS100 730 Origin_AS_PATH: {200, 100} 732 Capability Database: 733 CDN-Identifier: CDN2 734 Communities (std/ext): representing CDN2 capabilities 735 AS_PATH: 738 NLRI: CDN2-Prefix 740 CDN-Identifier: CDN3 741 Communities (std/ext): representing CDN capabilities 742 AS_PATH: 745 NLRI: CDN3-Prefix 747 The Footprint-Reachability and Capabilities databases also contains 748 the AS_PATH representing the MP-BGP connectivity in the CDNI Mesh and 749 the path taken by Footprint-Reachability Advertisements. It is 750 anyway mandatory in BGP for message loop prevention. 752 6.7. Request Routing for user 2.2.2.2 754 The following workflow is used for a request coming from user 755 2.2.2.2: 757 User with address 2.2.2.2 sends a content request to uCDN. 759 uCDN does a lookup in Footprint-Elements Database for address 760 2.2.2.2 and finds following entry: 762 2.2.2.0/24 763 AS_PATH: {, 400, 100} 765 uCDN does a lookup in Footprint-Reachability Database and look for 766 a CDN claiming connectivity to AS100. It finds following entry: 767 CDN-Identifier: CDN3 768 AS-PATH: {300} 770 Reachable Footprint-Element: AS300 771 Origin_AS_PATH: {} 773 Reachable Footprint-Element: AS100 774 Origin_AS_PATH: {200, 100} 776 uCDN can select CDN3 as downstream CDN. 778 6.8. Request Routing for user 1.1.1.1 780 The following workflow is used for a request coming from user 781 1.1.1.1: 783 User with address 1.1.1.1 sends a content request to uCDN. 785 uCDN does a lookup in Footprint-Elements Database for address 786 1.1.1.1 and finds following entries: 787 1.1.1.0/24 788 AS_PATH: {, 400, 100} 790 and 792 CDN2:1.1.1.0/24 793 AS_PATH: {CDN3, CDN2} 794 Footprint-Element Identifier: FP-CDN2 796 uCDN prefers the entry originated by a Footprint-Element 797 Advertisement and looks into the Footprint-Reachability Database 798 for a CDN claiming connectivity to Footprint-Element Identifier: 799 FP-CDN2. It finds following entries: 800 CDN-Identifier: CDN2 801 AS-PATH: {300, 200} 803 Reachable Footprint-Element: AS200 804 Origin_AS_PATH: {} 806 Reachable Footprint-Element: FP-CDN2 807 Origin_AS_PATH: {100} 809 uCDN can select CDN2 as downstream CDN 811 7. CDNI MP-BGP Encodings 813 This section describes the CDNI MP-BGP messages with their attributes 814 and NLRI encodings details. 816 7.1. CDNI Attributes 818 CDNI uses standard BGP attributes in both FPE and FPR advertisements 819 in addition to the following newly defined attributes: 821 FPE_Identifier is present in FPE advertisements (when identifying 822 an FPE as a set of prefixes) and FPR advertisements (when 823 identifying a reachable FPE). 825 CDN_Identifier is present in both FPE and FPR advertisements). 827 Origin_AS_PATH is present in FPR advertisements. 829 CDN Capabilities is present in CAP advertisements. 831 7.1.1. CDNI Identifier 833 CDN_Identifier is a mandatory transitive attribute consisting of an 834 extended community (type TBD) uniquely identifying the CDN within the 835 CDNI Mesh. CDNI_Identifier must be unique within the CDNI Mesh. The 836 recommended method is to use (as for the FPE_Identifier) the AS or IP 837 Address format as described in[RFC4360]. 839 7.1.2. FPE Identifier 841 FPE Identifier is a mandatory and transitive attribute consisting of 842 an extended community (type TBD) containing a Footprint Element 843 identifier. The FPE_Identifier uniquely identifies the FPE within 844 the CDNI Mesh. The format of the FPE_Identifier encodings should 845 ensure uniqueness of values. The recommended method for encoding 846 FPE_Identifier is to use the format as defined in RFC4360 and use 847 either the AS or an IP address owned by the CDN. This method, and 848 the extended community format, allows a CDN to create multiple unique 849 FPE_Identifiers. 851 7.1.3. Origin_AS_PATH 853 Origin_AS_PATH is an optional transitive attribute having the same 854 format as AS_PATH attribute and containing the AS_PATH value of the 855 Footprint Element known in the CDN originating the FPR advertisement. 857 Origin_AS_PATH must be left unchanged and has the same format as 858 AS_PATH BGP attribute as defined in [RFC4271]. 860 7.1.4. Capabilities 862 Capabilities is a mandatory and transitive attribute consisting of an 863 extended community (type TBD) containing a value representing a given 864 capability (TBD). More than one Capability attribute is allowed so 865 to allow a CDN to advertise multiple capabilities in the same 866 message. The encodings of Extended Communities is defined in: 867 [RFC4360]. 869 7.2. CDNI Messages 871 Three messages are used: FPE Advertisement, FPR Advertisement and CAP 872 Advertisement. 874 7.2.1. FPE Advertisement 876 Footprint Element Advertisement message is used by a CDN in order to 877 advertise a Footprint Element that can't be inferred from the BGP-4 878 Internet Database and that needs explicit advertisement. 880 The FPE Advertisement consists of one or more prefixes that a CDN 881 reaches. The FPE Advertisement scope is not to describe how the CDN 882 can reach the FPE but rather what are the prefixes forming the FPE. 883 The FPE Advertisement message should contain following information: 885 CDN_Identifier: uniquely identifies the CDN originating the 886 message. It is mandatory and transitive attribute. 887 CDN_Identifier format is described in Section 7.1. 889 Footprint-Element Identifier: a number uniquely identifying the 890 FPE as defined in Section 7.1. FPE-Identifier is encoded as an 891 extended community. It is mandatory and transitive. 893 Standard BGP attributes such as AS_PATH, Communities, 894 Local_Preference, MED, etc. are also used in the FPE Advertisement 895 Messages. 897 NLRI: the set of prefixes (address and mask) of the FPE. 899 A CDNI Distinguisher is prependd to each prefix of the FPE. The 900 CDNI Distingsuiher allows multiple CDNs to advertise the same 901 prefix in their FPE Advertisement. Each CDN must use a unique 902 number. The recommended method for assigning RDs is to use the 903 CDN AS number or an IP address owned by the CDN. 905 7.2.2. FPR Advertisement 907 Footprint Reachability Advertisement message is used by a CDN willing 908 to advertise the FPEs it can reach. The FPR Advertisement consists 909 of a set of FPE-Identifiers and their attributes. Following 910 information should be present in the FPR Advertisement message: 912 CDN_Identifier: uniquely identifies the CDN originating the 913 message. It is mandatory and transitive attribute. 914 CDN_Identifier format is described in Section 7.1. 916 Reachable Footprint-Element: one or more AS numbers and/or 917 FPE_Identifier representing the reachable FPEs. Reachable_FPE is 918 encoded as a set of extended communities. At least one must be 919 present in the message and the attribute is transitive. FPEs that 920 have been inferred from the BGP4 Internet database are identified 921 through their AS number and FPEs that have been explicitly 922 advertised are identified by their FPE_Identifier. 924 Standard BGP attributes such as AS_PATH, Communities, 925 Local_Preference, MED, etc. are also used in the FPR Advertisement 926 Messages. 928 Origin_AS_PATH. This attribute is related to an FPE and contains 929 the value of the BGP AS_PATH of the FPE in the CDN originating the 930 FPR message. When used, it implies all prefixes of the same FPE 931 share the same BGP AS_PATH in the CDN originating the FPR message. 933 NLRI: Reachable Footprint-Element: one or more FPE Identifiers 934 representing the reachable FPEs. Reachable FPE is encoded in the 935 CDNI NLRI. At least one must be present in the message. FPEs 936 that have been inferred from the BGP4 Internet database are 937 identified through their AS number and FPEs that have been 938 explicitly advertised are identified by their FPE Identifier. 940 7.2.3. CAP Advertisement 942 Capability Advertisement message is used by a CDN in order to 943 advertise its capabilities. Capabilities are encoded as a set of BGP 944 Extended Communities. The CAP Advertisement Message contains: 946 A CDN_Identifier: uniquely identifies the CDN originating the 947 message. It is mandatory and transitive attribute. 948 CDN_Identifier format is described in Section 7.1. 950 One or more Extended Communities attributes describing 951 capabilities. 953 Standard BGP attributes such as AS_PATH, Communities, 954 Local_Preference, MED, etc. are also used in the CAP Advertisement 955 Messages for policy reasons. 957 A CDN Prefix: a NLRI encoded prefix (IPv4 or IPv6) owned by the 958 CDN (i.e.: a prefix that is part of the address space of the CDN). 960 7.3. CDNI NLRI 962 Multiprotocol-BGP defines two attributes, MP_REACH and MP_UNREACH, 963 that are BGP's containers for carrying opaque information. Each CDNI 964 NLRI describes either a FPE or a FPR. 966 All FPE and FPR information SHALL be encoded using AFI 1 or 2 (ipv4 967 or ipv6) with a TBD (CDNI) SAFI. 969 In order for two BGP speakers to exchange CDNI NLRI, they MUST use 970 BGP Capabilities Advertisement to ensure that they both are capable 971 of properly processing CDNI NLRI. This is done as specified in 972 [RFC4760], by using capability code 1 (multi-protocol BGP), with the 973 AFI: 1 or 2, SAFI: TBD. 975 0 1 2 3 976 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 977 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 978 | NLRI Type | Total NLRI Length | 979 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 980 | | 981 | CDNI NLRI (variable) | 982 | | 983 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 985 where: 986 NLRI Type: 1 (FPE) 987 2 (FPR) 988 3 (CAP) 990 7.3.1. CDNI-NLRI Type 1: FPE Advertisement 991 0 1 2 3 992 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 993 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 994 | NLRI Type: 1 | Total NLRI Length | 995 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 996 | | 997 + CDNI FPE Distinguisher + 998 | | 999 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1000 | | 1001 | IPv4/IPv6 NLRI (variable) | 1002 | | 1003 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1005 where: 1006 NLRI Type: 1 specifies the FPE Advertisement 1007 CDNI FPE Distinguisher: 8 octets 1008 NLRI: IPv4 or IPv6 prefix 1010 7.3.2. CDNI-NLRI Type 2: FPR Advertisement 1012 0 1 2 3 1013 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1014 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1015 | NLRI Type: 2 | Total NLRI Length | 1016 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1017 | | 1018 + Connected FPEs (variable) + 1019 | | 1020 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1022 where: 1023 NLRI Type 2 specifies the FPR Advertisement 1024 Connected FPEs: set of FPE Identifiers representing the FPEs the 1025 CDN can reach. 1027 7.3.3. CDNI-NLRI Type 3: CAP Advertisement 1028 0 1 2 3 1029 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 2 3 4 5 6 7 8 9 0 1 1030 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1031 | NLRI Type: 3 | Total NLRI Length | 1032 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1033 | | 1034 + IPv4/IPv6 NLRI + 1035 | | 1036 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 1038 where: 1039 NLRI Type 3 specifies the CAP Advertisement 1040 NLRI: IPv4 or IPv6 prefix 1042 7.3.4. NLRI Encoding 1044 The Network Layer Reachability Information contains one or more IPv4 1045 or IPv6 prefixes, according to AFI value, and is encoded as one or 1046 more 2-tuples of the form , whose fields are 1047 described below: 1048 +---------------------------+ 1049 | Length (1 octet) | 1050 +---------------------------+ 1051 | Prefix (variable) | 1052 +---------------------------+ 1054 where: 1055 Length: the Length field indicates the length in bits of the IP 1056 address prefix. A length of zero indicates a prefix that matches 1057 all IP addresses (with prefix, itself, of zero octets). 1059 Prefix: the Prefix field contains an IP address prefix, followed 1060 by enough trailing bits to make the end of the field fall on an 1061 octet boundary. Note that the value of the trailing bits is 1062 irrelevant. 1064 In the FPE Advertisement message, the NLRI contains the set of 1065 prefixes part of the FPE to be advertised. 1067 In the CAP Advertisement message, the NLRI contains a prefix ownded 1068 by the CDN. 1070 It has to be noted that a CDN may use multiple FPR messages for 1071 advertising reachability to multiple FPEs. In such cases multiple 1072 NLRI prefixes would be needed in order not to create collisions in 1073 the BGP selection process (that would select only one NLRI message 1074 among the ones having identical NLRI prefixes). 1076 8. Compliance with CDNI Requirements 1078 [I-D.ietf-cdni-requirements] outlines the requirements for the 1079 solution and interfaces to be specified by the CDNI working group. 1080 This section identifies the relevant requirements from that document 1081 and discusses compliance by the solution proposed in this document. 1083 [Editor's Note: Text is to be added when requirements-03 is 1084 available. This needs to discuss the requirements labeled R27, R28, 1085 R29 and R30 as of requirements-02]. 1087 9. IANA Considerations 1089 none. 1091 10. Security Considerations 1093 This draft does not affect the BGP security model. 1095 11. Acknowledgements 1097 The authors would like to thank Steven Luong, Manish Bhardwaj and 1098 Bruce Davie for their contributions. 1100 12. References 1102 12.1. Normative References 1104 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 1105 Requirement Levels", BCP 14, RFC 2119, March 1997. 1107 [RFC4271] Rekhter, Y., Li, T., and S. Hares, "A Border Gateway 1108 Protocol 4 (BGP-4)", RFC 4271, January 2006. 1110 [RFC4360] Sangli, S., Tappan, D., and Y. Rekhter, "BGP Extended 1111 Communities Attribute", RFC 4360, February 2006. 1113 [RFC4364] Rosen, E. and Y. Rekhter, "BGP/MPLS IP Virtual Private 1114 Networks (VPNs)", RFC 4364, February 2006. 1116 [RFC4760] Bates, T., Chandra, R., Katz, D., and Y. Rekhter, 1117 "Multiprotocol Extensions for BGP-4", RFC 4760, 1118 January 2007. 1120 12.2. Informative References 1122 [I-D.bertrand-cdni-use-cases] 1123 Bertrand, G., Stephan, E., Watson, G., Burbridge, T., 1124 Eardley, P., and K. Ma, "Use Cases for Content Delivery 1125 Network Interconnection", draft-bertrand-cdni-use-cases-02 1126 (work in progress), July 2011. 1128 [I-D.davie-cdni-framework] 1129 Davie, B. and L. Peterson, "Framework for CDN 1130 Interconnection", draft-davie-cdni-framework-01 (work in 1131 progress), October 2011. 1133 [I-D.ietf-cdni-requirements] 1134 Leung, K. and Y. Lee, "Content Distribution Network 1135 Interconnection (CDNI) Requirements", 1136 draft-ietf-cdni-requirements-03 (work in progress), 1137 June 2012. 1139 [I-D.jenkins-cdni-problem-statement] 1140 Niven-Jenkins, B., Faucheur, F., and N. Bitar, "Content 1141 Distribution Network Interconnection (CDNI) Problem 1142 Statement", draft-jenkins-cdni-problem-statement-02 (work 1143 in progress), March 2011. 1145 Authors' Addresses 1147 Stefano Previdi (editor) 1148 Cisco Systems, Inc. 1149 Via Del Serafico 200 1150 Rome 00191 1151 IT 1153 Email: sprevidi@cisco.com 1155 Francois Le Faucheur 1156 Cisco Systems, Inc. 1157 Greenside, 400 Avenue de Roumanille 1158 Sophia Antipolis 06410 1159 FR 1161 Email: flefauch@cisco.com 1162 Jan Medved 1163 Cisco Systems, Inc. 1164 3700 Cisco Way 1165 SAN JOSE, CA 95134 1166 US 1168 Email: jmedved@cisco.com 1170 Allan Guillou 1171 SFR 1172 40-42 Quai du Point du Jour 1173 Boulogne-Billancourt 92659 1174 FR 1176 Email: allan.guillou@sfr.com