idnits 2.17.1 draft-bonica-6man-comp-rtg-hdr-16.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 : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year -- The document date (May 13, 2020) is 1441 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) -- Looks like a reference, but probably isn't: '0' on line 593 -- Looks like a reference, but probably isn't: '1' on line 574 == Unused Reference: 'RFC4443' is defined on line 429, but no explicit reference was found in the text Summary: 0 errors (**), 0 flaws (~~), 2 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 2 6man R. Bonica 3 Internet-Draft Juniper Networks 4 Intended status: Standards Track Y. Kamite 5 Expires: November 14, 2020 NTT Communications Corporation 6 T. Niwa 7 KDDI 8 A. Alston 9 Liquid Telecom 10 L. Jalil 11 Verizon 12 May 13, 2020 14 The IPv6 Compressed Routing Header (CRH) 15 draft-bonica-6man-comp-rtg-hdr-16 17 Abstract 19 This document defines two new Routing header types. Collectively, 20 they are called the Compressed Routing Headers (CRH). Individually, 21 they are called CRH-16 and CRH-32. 23 Status of This Memo 25 This Internet-Draft is submitted in full conformance with the 26 provisions of BCP 78 and BCP 79. 28 Internet-Drafts are working documents of the Internet Engineering 29 Task Force (IETF). Note that other groups may also distribute 30 working documents as Internet-Drafts. The list of current Internet- 31 Drafts is at https://datatracker.ietf.org/drafts/current/. 33 Internet-Drafts are draft documents valid for a maximum of six months 34 and may be updated, replaced, or obsoleted by other documents at any 35 time. It is inappropriate to use Internet-Drafts as reference 36 material or to cite them other than as "work in progress." 38 This Internet-Draft will expire on November 14, 2020. 40 Copyright Notice 42 Copyright (c) 2020 IETF Trust and the persons identified as the 43 document authors. All rights reserved. 45 This document is subject to BCP 78 and the IETF Trust's Legal 46 Provisions Relating to IETF Documents 47 (https://trustee.ietf.org/license-info) in effect on the date of 48 publication of this document. Please review these documents 49 carefully, as they describe your rights and restrictions with respect 50 to this document. Code Components extracted from this document must 51 include Simplified BSD License text as described in Section 4.e of 52 the Trust Legal Provisions and are provided without warranty as 53 described in the Simplified BSD License. 55 Table of Contents 57 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2 58 2. Requirements Language . . . . . . . . . . . . . . . . . . . . 3 59 3. The Compressed Routing Headers (CRH) . . . . . . . . . . . . 3 60 4. The CRH Forwarding Information Base (CRH-FIB) . . . . . . . 5 61 5. Processing Rules . . . . . . . . . . . . . . . . . . . . . . 5 62 5.1. Computing Minimum CRH Length . . . . . . . . . . . . . . 6 63 6. Mutability . . . . . . . . . . . . . . . . . . . . . . . . . 7 64 7. Applications And SIDs . . . . . . . . . . . . . . . . . . . . 7 65 8. Management Considerations . . . . . . . . . . . . . . . . . . 8 66 9. Security Considerations . . . . . . . . . . . . . . . . . . . 8 67 10. Implementation and Deployment Status . . . . . . . . . . . . 8 68 11. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 8 69 12. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9 70 13. Contributors . . . . . . . . . . . . . . . . . . . . . . . . 9 71 14. References . . . . . . . . . . . . . . . . . . . . . . . . . 10 72 14.1. Normative References . . . . . . . . . . . . . . . . . . 10 73 14.2. Informative References . . . . . . . . . . . . . . . . . 10 74 Appendix A. CRH Processing Examples . . . . . . . . . . . . . . 11 75 Appendix B. CRH Processing Examples . . . . . . . . . . . . . . 12 76 B.1. The SID List Contains One Entry For Each Segment In The 77 Path . . . . . . . . . . . . . . . . . . . . . . . . . . 13 78 B.2. The SID List Omits The First Entry In The Path . . . . . 14 79 Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 14 81 1. Introduction 83 IPv6 [RFC8200] source nodes use Routing headers to specify the path 84 that a packet takes to its destination. The IETF has defined several 85 Routing header types [IANA-RH]. This document defines two new 86 Routing header types. Collectively, they are called the Compressed 87 Routing Headers (CRH). Individually, they are called CRH-16 and CRH- 88 32. 90 The CRH allows IPv6 source nodes to specify the path that a packet 91 takes to its destination. The CRH: 93 o Can be encoded in relatively few bytes. 95 o Is designed to operate within a network domain. (See Section 9). 97 The following are reasons for encoding the CRH in as few bytes as 98 possible: 100 o Many ASIC-based forwarders copy all headers from buffer memory to 101 on-chip memory. As header sizes increase, so does the cost of 102 this copy. 104 o Because Path MTU Discovery (PMTUD) [RFC8201] is not entirely 105 reliable, many IPv6 hosts refrain from sending packets larger than 106 the IPv6 minimum link MTU (i.e., 1280 bytes). When packets are 107 small, the overhead imposed by large Routing Headers is excessive. 109 Section 9 of this document addresses security considerations. 110 Appendix A of this document demonstrates how the CRH can be encoded 111 in fewer bytes than RH0. 113 2. Requirements Language 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "NOT RECOMMENDED", "MAY", and 117 "OPTIONAL" in this document are to be interpreted as described in BCP 118 14 [RFC2119] [RFC8174] when, and only when, they appear in all 119 capitals, as shown here. 121 3. The Compressed Routing Headers (CRH) 123 Both CRH versions (i.e., CRH-16 and CRH-32) contain the following 124 fields: 126 o Next Header - Defined in [RFC8200]. 128 o Hdr Ext Len - Defined in [RFC8200]. 130 o Routing Type - Defined in [RFC8200]. Value TBD by IANA. (For 131 CRH-16, the suggested value is 5. For CRH-32, the suggested value 132 is 6.) 134 o Segments Left - Defined in [RFC8200]. 136 o Type-specific Data - Described in [RFC8200]. 138 In the CRH, the Type-specific data field contains a list of Segment 139 Identifiers (SIDs). Each SID represents both of the following: 141 o A segment of the path that the packet takes to its destination. 143 o An entry in the CRH Forwarding Information Base (CRH-FIB) 144 (Section 4). 146 SIDs are listed in reverse order. So, the first SID in the list 147 represents the final segment in the path. Because segments are 148 listed in reverse order, the Segments Left field can be used as an 149 index into the SID list. In this document, the "current SID" is the 150 SID list entry referenced by the Segments Left field. 152 The first segment in the path can be omitted from the list. See 153 (Appendix B) for examples. 155 In the CRH-16 (Figure 1), each SID is encoded in 16-bits. In the 156 CRH-32 (Figure 2), each SID is encoded in 32-bits. 158 In all cases, the CRH MUST end on a 64-bit boundary. So, the Type- 159 specific data field MUST be padded with zeros if the CRH would 160 otherwise not end on a 64-bit boundary. 162 0 1 2 3 163 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 164 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 165 | Next Header | Hdr Ext Len | Routing Type | Segments Left | 166 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 167 | SID[0] | SID[1] | 168 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-| 169 | ......... 170 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+- 172 Figure 1: CRH-16 174 0 1 2 3 175 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 176 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 177 | Next Header | Hdr Ext Len | Routing Type | Segments Left | 178 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 179 + SID[0] + 180 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 181 + SID[1] + 182 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 183 // // 184 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 185 + SID[n] + 186 +-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+-+ 188 Figure 2: CRH-32 190 4. The CRH Forwarding Information Base (CRH-FIB) 192 Each SID identifies a CRH-FIB entry. 194 Each CRH-FIB entry contains: 196 o A IPv6 address. 198 o A forwarding method. 200 o Method-specific parameters (optional). 202 The IPv6 address represents an interface on the next segment 203 endpoint. It MUST NOT be a link-local address. While the IPv6 204 address represents an interface on the next segment endpoint, it does 205 not necessarily represent the interface through which the packet will 206 arrive at the next segment endpoint. 208 The forwarding method specifies how the processing node will forward 209 the packet to the next segment endpoint. The following are examples: 211 o Forward the packet to the next-hop along the least-cost path to 212 the next segment endpoint. 214 o Forward the packet through a specified interface to the next 215 segment endpoint. 217 Some forwarding methods require method-specific parameters. For 218 example, a forwarding method might require a parameter that 219 identifies the interface through which the packet should be 220 forwarded. 222 The CRH-FIB can be populated: 224 o By an operator, using a Command Line Interface (CLI). 226 o By a controller, using the Path Computation Element (PCE) 227 Communication Protocol (PCEP) [RFC5440] or the Network 228 Configuration Protocol (NETCONF) [RFC6241]. 230 o By a distributed routing protocol [ISO10589-Second-Edition], 231 [RFC5340], [RFC4271]. 233 5. Processing Rules 235 The following rules describe CRH processing: 237 o If Segments Left equals 0, skip over the CRH and process the next 238 header in the packet. 240 o If Hdr Ext Len indicates that the CRH is larger than the 241 implementation can process, discard the packet and send an ICMPv6 242 Parameter Problem, Code 0, message to the Source Address, pointing 243 to the Hdr Ext Len field. 245 o Compute L, the minimum CRH length (See (Section 5.1)). 247 o If L is greater than Hdr Ext Len, discard the packet and send an 248 ICMPv6 Parameter Problem, Code 0, message to the Source Address, 249 pointing to the Segments Left field. 251 o Decrement Segments Left. 253 o Search for the current SID in the CRH-FIB. In this document, the 254 "current SID" is the SID list entry referenced by the Segments 255 Left field. 257 o If the search does not return a CRH-FIB entry, discard the packet 258 and send an ICMPv6 Parameter Problem, Code 0, message to the 259 Source Address, pointing to the current SID. 261 o If Segments Left is greater than 0 and the CRH-FIB entry contains 262 a multicast address, discard the packet and send an ICMPv6 263 Parameter Problem, Code 0, message to the Source Address, pointing 264 to the current SID. 266 o Copy the IPv6 address from the CRH-FIB entry to the Destination 267 Address field in the IPv6 header. 269 o Decrement the IPv6 Hop Limit. 271 o Resubmit the packet to the IPv6 module for transmission to the new 272 destination, ensuring that it executes the forwarding method 273 specified by the CRH-FIB entry. 275 5.1. Computing Minimum CRH Length 277 The algorithm described in this section accepts the following CRH 278 fields as its input parameters: 280 o Routing Type (i.e., CRH-16 or CRH-32). 282 o Segments Left. 284 It yields L, the minimum CRH length. The minimum CRH length is 285 measured in 8-octet units, not including the first 8 octets. 287 289 switch(Routing Type) { 290 case CRH-16: 291 if (Segments Left <= 2) 292 return(0) 293 sidsBeyondFirstWord = Segments Left - 2; 294 sidPerWord = 4; 295 case CRH-32: 296 if (Segments Left <= 1) 297 return(0) 298 sidsBeyondFirstWord = Segments Left - 1; 299 sidsPerWord = 2; 300 case default: 301 return(0xFF); 302 } 304 words = sidsBeyondFirstWord div sidsPerWord; 305 if (sidsBeyondFirstWord mod sidsPerWord) 306 words++; 308 return(words) 310 312 6. Mutability 314 In the CRH, the Segments Left field is mutable. All remaining fields 315 are immutable. 317 7. Applications And SIDs 319 A CRH contains one or more SIDs. Each SID is processed by exactly 320 one node. 322 Therefore, a SID is not required to have domain-wide significance. 323 Applications can: 325 o Allocate SIDs so that they have domain-wide significance. 327 o Allocate SIDs so that they have node-local significance. 329 8. Management Considerations 331 PING and TRACEROUTE [RFC2151] both operate correctly in the presence 332 of the CRH. 334 9. Security Considerations 336 Networks that process the CRH MUST NOT accept packets containing the 337 CRH from untrusted sources. Their border routers SHOULD discard 338 packets that satisfy the following criteria: 340 o The packet contains a CRH 342 o The Segments Left field in the CRH has a value greater than 0 344 o The Destination Address field in the IPv6 header represents an 345 interface that resides inside of the network. 347 Many border routers cannot filter packets based upon the Segments 348 Left value. These border routers MAY discard packets that satisfy 349 the following criteria: 351 o The packet contains a CRH 353 o The Destination Address field in the IPv6 header represents an 354 interface that resides inside of the network. 356 10. Implementation and Deployment Status 358 Juniper Networks has produced experimental implementations of the CRH 359 on: 361 o A LINUX-based software platform 363 o The MX-series (ASIC-based) router 365 Liquid Telecom has deployed the CRH, on a limited basis, in their 366 network. Other experimental deployments are in progress. 368 11. IANA Considerations 370 SID values 0-15 are reserved for future use. They may be assigned by 371 IANA, based on IETF Consensus. IANA is requested to establish a 372 "Registry of SRm6 Reserved SIDs". Values 0-15 are reserved for 373 future use. 375 IANA is requested to make the following entries in the Internet 376 Protocol Version 6 (IPv6) Parameters "Routing Type" registry 377 [IANA-RH]: 379 Suggested 380 Value Description Reference 381 --------------------------------------------------------------------- 382 5 Compressed Routing Header (16-bit) (CRH-16) This document 383 6 Compressed Routing Header (32-bit) (CRH-32) This document 385 12. Acknowledgements 387 Thanks to Dr. Vanessa Ameen, Fernando Gont, Naveen Kottapalli, Joel 388 Halpern, Tony Li, Gerald Schmidt, Nancy Shaw, and Chandra Venkatraman 389 for their contributions to this document. 391 13. Contributors 393 Daniam Henriques 395 Liquid Telecom 397 Johannesburg, South Africa 399 Email: daniam.henriques@liquidtelecom.com 401 Gang Chen 403 Baidu 405 No.10 Xibeiwang East Road Haidian District 407 Beijing 100193 P.R. China 409 Email: phdgang@gmail.com 411 Yifeng Zhou 413 ByteDance 415 Building 1, AVIC Plaza, 43 N 3rd Ring W Rd Haidian District 417 Beijing 100000 P.R. China 418 Email: yifeng.zhou@bytedance.com 420 14. References 422 14.1. Normative References 424 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 425 Requirement Levels", BCP 14, RFC 2119, 426 DOI 10.17487/RFC2119, March 1997, 427 . 429 [RFC4443] Conta, A., Deering, S., and M. Gupta, Ed., "Internet 430 Control Message Protocol (ICMPv6) for the Internet 431 Protocol Version 6 (IPv6) Specification", STD 89, 432 RFC 4443, DOI 10.17487/RFC4443, March 2006, 433 . 435 [RFC8174] Leiba, B., "Ambiguity of Uppercase vs Lowercase in RFC 436 2119 Key Words", BCP 14, RFC 8174, DOI 10.17487/RFC8174, 437 May 2017, . 439 [RFC8200] Deering, S. and R. Hinden, "Internet Protocol, Version 6 440 (IPv6) Specification", STD 86, RFC 8200, 441 DOI 10.17487/RFC8200, July 2017, 442 . 444 [RFC8201] McCann, J., Deering, S., Mogul, J., and R. Hinden, Ed., 445 "Path MTU Discovery for IP version 6", STD 87, RFC 8201, 446 DOI 10.17487/RFC8201, July 2017, 447 . 449 14.2. Informative References 451 [IANA-RH] IANA, "Routing Headers", 452 . 455 [ISO10589-Second-Edition] 456 International Organization for Standardization, 457 ""Intermediate system to Intermediate system intra-domain 458 routeing information exchange protocol for use in 459 conjunction with the protocol for providing the 460 connectionless-mode Network Service (ISO 8473)", ISO/IEC 461 10589:2002, Second Edition,", November 2001. 463 [RFC2151] Kessler, G. and S. Shepard, "A Primer On Internet and TCP/ 464 IP Tools and Utilities", FYI 30, RFC 2151, 465 DOI 10.17487/RFC2151, June 1997, 466 . 468 [RFC4271] Rekhter, Y., Ed., Li, T., Ed., and S. Hares, Ed., "A 469 Border Gateway Protocol 4 (BGP-4)", RFC 4271, 470 DOI 10.17487/RFC4271, January 2006, 471 . 473 [RFC5340] Coltun, R., Ferguson, D., Moy, J., and A. Lindem, "OSPF 474 for IPv6", RFC 5340, DOI 10.17487/RFC5340, July 2008, 475 . 477 [RFC5440] Vasseur, JP., Ed. and JL. Le Roux, Ed., "Path Computation 478 Element (PCE) Communication Protocol (PCEP)", RFC 5440, 479 DOI 10.17487/RFC5440, March 2009, 480 . 482 [RFC6241] Enns, R., Ed., Bjorklund, M., Ed., Schoenwaelder, J., Ed., 483 and A. Bierman, Ed., "Network Configuration Protocol 484 (NETCONF)", RFC 6241, DOI 10.17487/RFC6241, June 2011, 485 . 487 Appendix A. CRH Processing Examples 489 The CRH-16 and CRH-32 encode information more efficiently than RH0. 491 +------+-----+--------+--------+ 492 | SIDs | RH0 | CRH-16 | CRH-32 | 493 +------+-----+--------+--------+ 494 | 1 | 24 | 8 | 8 | 495 | 2 | 40 | 8 | 16 | 496 | 3 | 56 | 16 | 16 | 497 | 4 | 72 | 16 | 24 | 498 | 5 | 88 | 16 | 24 | 499 | 6 | 104 | 16 | 32 | 500 | 7 | 120 | 24 | 32 | 501 | 8 | 136 | 24 | 40 | 502 | 9 | 152 | 24 | 40 | 503 | 10 | 168 | 24 | 48 | 504 | 11 | 184 | 32 | 48 | 505 | 12 | 200 | 32 | 52 | 506 | 13 | 216 | 32 | 52 | 507 | 14 | 232 | 32 | 56 | 508 | 15 | 248 | 40 | 56 | 509 | 16 | 264 | 40 | 60 | 510 | 17 | 280 | 40 | 60 | 511 | 18 | 296 | 40 | 64 | 512 +------+-----+--------+--------+ 514 Table 1: Routing Header Size (in Bytes) As A Function Of Routing 515 Header Type and Number Of SIDs 517 (Table 1) reflects Routing header size as a function of Routing 518 header type and number of SIDs contained by the Routing header. 520 Appendix B. CRH Processing Examples 522 This appendix demonstrates CRH processing in the following scenarios: 524 o The SID list contains one entry for each segment in the path 525 (Appendix B.1). 527 o The SID list omits the first entry in the path (Appendix B.2). 529 ----------- ----------- ----------- 530 |Node: S | |Node: I1 | |Node: I2 | 531 |Loopback: |---------------|Loopback: |---------------|Loopback: | 532 |2001:db8::a| |2001:db8::1| |2001:db8::2| 533 ----------- ----------- ----------- 534 | | 535 | ----------- | 536 | |Node: D | | 537 ---------------------|Loopback: |--------------------- 538 |2001:db8::b| 539 ----------- 541 Figure 3: Reference Topology 543 Figure 3 provides a reference topology that is used in all examples. 545 +-----+--------------+-------------------+ 546 | SID | IPv6 Address | Forwarding Method | 547 +-----+--------------+-------------------+ 548 | 2 | 2001:db8::2 | Least-cost path | 549 | 11 | 2001:db8::b | Least-cost path | 550 +-----+--------------+-------------------+ 552 Table 2: Node SIDs 554 Table 2 describes two entries that appear in each node's CRH-FIB. 556 B.1. The SID List Contains One Entry For Each Segment In The Path 558 In this example, Node S sends a packet to Node D, via I2. In this 559 example, I2 appears in the CRH segment list. 561 +-------------------------------------+-------------------+ 562 | As the packet travels from S to I2: | | 563 +-------------------------------------+-------------------+ 564 | Source Address = 2001:db8::a | Segments Left = 1 | 565 | Destination Address = 2001:db8::2 | SID[0] = 11 | 566 | | SID[1] = 2 | 567 +-------------------------------------+-------------------+ 569 +-------------------------------------+-------------------+ 570 | As the packet travels from I2 to D: | | 571 +-------------------------------------+-------------------+ 572 | Source Address = 2001:db8::a | Segments Left = 0 | 573 | Destination Address = 2001:db8::b | SID[0] = 11 | 574 | | SID[1] = 2 | 575 +-------------------------------------+-------------------+ 577 B.2. The SID List Omits The First Entry In The Path 579 In this example, Node S sends a packet to Node D, via I2. In this 580 example, I2 does not appear in the CRH segment list. 582 +-------------------------------------+-------------------+ 583 | As the packet travels from S to I2: | | 584 +-------------------------------------+-------------------+ 585 | Source Address = 2001:db8::a | Segments Left = 1 | 586 | Destination Address = 2001:db8::2 | SID[0] = 11 | 587 +-------------------------------------+-------------------+ 589 +-------------------------------------+-------------------+ 590 | As the packet travels from I2 to D: | | 591 +-------------------------------------+-------------------+ 592 | Source Address = 2001:db8::a | Segments Left = 0 | 593 | Destination Address = 2001:db8::b | SID[0] = 11 | 594 +-------------------------------------+-------------------+ 596 Authors' Addresses 598 Ron Bonica 599 Juniper Networks 600 2251 Corporate Park Drive 601 Herndon, Virginia 20171 602 USA 604 Email: rbonica@juniper.net 606 Yuji Kamite 607 NTT Communications Corporation 608 3-4-1 Shibaura, Minato-ku 609 Tokyo 108-8118 610 Japan 612 Email: y.kamite@ntt.com 614 Tomonobu Niwa 615 KDDI 616 3-22-7, Yoyogi, Shibuya-ku 617 Tokyo 151-0053 618 Japan 620 Email: to-niwa@kddi.com 621 Andrew Alston 622 Liquid Telecom 623 Nairobi 624 Kenya 626 Email: Andrew.Alston@liquidtelecom.com 628 Luay Jalil 629 Verizon 630 Richardson, Texas 631 USA 633 Email: luay.jalil@one.verizon.com