Guest User

Untitled

a guest
Nov 10th, 2020
492
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
  1. 64share-V2 C. Byrne
  2. Internet Draft T-Mobile USA
  3. Intended status: Informational November 9, 2020
  4. Expires: May 2021
  5.  
  6.  
  7.  
  8. 64share-V2
  9. draft-byrne-v6ops-64sharev2-00.txt
  10.  
  11.  
  12. Abstract
  13.  
  14. In a 3GPP wireless network, the IPv6 radio interfaces must be
  15. provided as an off-link /64 using RA. This memo updates that
  16. requirement, through liaison with the 3GPP, to allow any legitimate
  17. prefix size less than or equal to /64 be allocated from the 3GPP
  18. network gateway to the UE using RA. This modification allows a UE to
  19. assign and delegate prefixes to attached and downstream networks.
  20.  
  21. Status of this Memo
  22.  
  23. This Internet-Draft is submitted in full conformance with the
  24. provisions of BCP 78 and BCP 79.
  25.  
  26. This document may contain material from IETF Documents or IETF
  27. Contributions published or made publicly available before November
  28. 10, 2008. The person(s) controlling the copyright in some of this
  29. material may not have granted the IETF Trust the right to allow
  30. modifications of such material outside the IETF Standards Process.
  31. Without obtaining an adequate license from the person(s) controlling
  32. the copyright in such materials, this document may not be modified
  33. outside the IETF Standards Process, and derivative works of it may
  34. not be created outside the IETF Standards Process, except to format
  35. it for publication as an RFC or to translate it into languages other
  36. than English.
  37.  
  38. Internet-Drafts are working documents of the Internet Engineering
  39. Task Force (IETF), its areas, and its working groups. Note that
  40. other groups may also distribute working documents as Internet-
  41. Drafts.
  42.  
  43. Internet-Drafts are draft documents valid for a maximum of six months
  44. and may be updated, replaced, or obsoleted by other documents at any
  45. time. It is inappropriate to use Internet-Drafts as reference
  46. material or to cite them other than as "work in progress."
  47.  
  48.  
  49.  
  50.  
  51.  
  52. Byrne Expires May 9, 2021 [Page 1]
  53.  
  54. Internet-Draft 64share-V2 November 2020
  55.  
  56.  
  57. The list of current Internet-Drafts can be accessed at
  58. http://www.ietf.org/ietf/1id-abstracts.txt
  59.  
  60. The list of Internet-Draft Shadow Directories can be accessed at
  61. http://www.ietf.org/shadow.html
  62.  
  63. This Internet-Draft will expire on May 9, 2009.
  64.  
  65. Copyright Notice
  66.  
  67. Copyright (c) 2020 IETF Trust and the persons identified as the
  68. document authors. All rights reserved.
  69.  
  70. This document is subject to BCP 78 and the IETF Trust's Legal
  71. Provisions Relating to IETF Documents
  72. (http://trustee.ietf.org/license-info) in effect on the date of
  73. publication of this document. Please review these documents
  74. carefully, as they describe your rights and restrictions with respect
  75. to this document.
  76.  
  77. Table of Contents
  78.  
  79.  
  80. 1. Introduction...................................................2
  81. 2. Delegating IPv6 Prefixes to a 3GPP UE via Router Advertisements3
  82. 3. Consuming, Assigning, and Delegating the RA Assigned Prefix....3
  83. 4. Security Considerations........................................3
  84. 5. IANA Considerations............................................3
  85. 6. Summary and Conclusions........................................3
  86. 7. Acknowledgments................................................4
  87. 8. References.....................................................4
  88. 8.1. Normative References......................................4
  89. 8.2. Informative References....................................4
  90.  
  91. 1. Introduction
  92.  
  93. 3GPP wireless networks assign an IPv6 /64 off-link prefix to each
  94. user equipment (UE) attachment [RFC 6459]. This has enabled the
  95. widely deployed sharing of the 3GPP wireless link prefix to hosts on
  96. an attached LAN [RFC 7278]. This model is limited to a single /64
  97. and is therefore not fit for anything more than the simplest of
  98. scenarios.
  99.  
  100. While DHCPv6 Prefix Delegation (PD) [RFC 3633] is optionally
  101. supported in the 3GPP standard for providing larger IPv6 prefix
  102. allocations to UEs, it has not seen any a commercial deployment in
  103. 3GPP networks. This memo does not speculate on the challenges of
  104.  
  105.  
  106. Byrne Expires May 9, 2021 [Page 2]
  107.  
  108. Internet-Draft 64share-V2 November 2020
  109.  
  110.  
  111. deploying DHCPv6 PD, it simply acknowledges that another way may
  112. result in quicker and broader deployment of larger more useful IPv6
  113. allocations.
  114.  
  115. 2. Delegating IPv6 Prefixes to a 3GPP UE via Router Advertisements
  116.  
  117. As described in [RFC 6459], the 3GPP network may only assign a single
  118. off-link /64 per bearer attachment. This assignment is passed from
  119. the gateway to the UE using a router advertisement (RA)[RFC 4861].
  120. This memo requests the 3GPP to change this requirement to allow any
  121. prefix size less than or equal to 64 be advertised by the 3GPP
  122. gateway RA.
  123.  
  124. This change allows the UE to be given a prefix such as a /56 using
  125. RA, which is consider sufficient for a home network. As wireless
  126. networks are playing a larger role in delivery home broadband as well
  127. as other complex network scenarios, the need to deliver greater than
  128. a single /64 is imperative.
  129.  
  130. 3. Consuming, Assigning, and Delegating the RA Assigned Prefix
  131.  
  132. Once the UE has received the off-link less than 64 bit prefix, it may
  133. use the prefix in any legitimate manner. For example, the host
  134. configuration may have defined configuration rules that state if a
  135. /56 is received from the 3GPP network, it will assign a /64 to the
  136. wireless LAN interface, another /64 is to be used for a CLAT [RFC
  137. 6877], and the remainder of addresses will create a pool of prefixes
  138. that are assigned to downstream DHCPv6 PD clients.
  139.  
  140. 4. Security Considerations
  141.  
  142. TBD
  143.  
  144. 5. IANA Considerations
  145.  
  146. TBD
  147.  
  148. 6. Summary and Conclusions
  149.  
  150. This memo requests that the 3GPP modify its IPv6 assignment
  151. restrictions to facilitate RA assignment of IPv6 prefixes less than
  152. or equal to /64. It also guides UE deployments to use these larger
  153. allocations of IPv6 addresses to assign and delegate to downstream
  154. systems.
  155.  
  156.  
  157.  
  158.  
  159.  
  160. Byrne Expires May 9, 2021 [Page 3]
  161.  
  162. Internet-Draft 64share-V2 November 2020
  163.  
  164.  
  165. 7. Acknowledgments
  166.  
  167. TBD.
  168.  
  169.  
  170.  
  171. 8. References
  172.  
  173. 8.1. Normative References
  174.  
  175. [RFC4861] Narten, T., Nordmark, E., Simpson, W., and H. Soliman,
  176. "Neighbor Discovery for IP version 6 (IPv6)", RFC 4861,
  177. DOI 10.17487/RFC4861, September 2007,
  178. <https://www.rfc-editor.org/info/rfc4861>.
  179.  
  180. 8.2. Informative References
  181.  
  182. [RFC3633] Troan, O. and R. Droms, "IPv6 Prefix Options for Dynamic
  183. Host Configuration Protocol (DHCP) version 6", RFC 3633,
  184. December 2003, <http://www.rfc-editor.org/info/rfc3633>.
  185.  
  186. [RFC6459] Korhonen, J., Soininen, J., Patil, B., Savolainen, T.,
  187. Bajko, G., and K. Iisakkila, "IPv6 in 3rd Generation
  188. Partnership Project (3GPP) Evolved Packet System (EPS)",
  189. RFC 6459, January 2012, <http://www.rfc-
  190. editor.org/info/rfc6459>.
  191.  
  192. [RFC6877] Mawatari, M., Kawashima, M., and C. Byrne, "464XLAT:
  193. Combination of Stateful and Stateless Translation",
  194. RFC 6877, DOI 10.17487/RFC6877, April 2013,
  195. <https://www.rfc-editor.org/info/rfc6877>.
  196.  
  197. [RFC7278] Byrne, C., Drown, D., and A. Vizdal, "Extending an IPv6
  198. /64 Prefix from a Third Generation Partnership Project
  199. (3GPP) Mobile Interface to a LAN Link", RFC 7278, June
  200. 2014, <http://www.rfc-editor.org/info/rfc7278>.
  201.  
  202.  
  203.  
  204. Authors' Addresses
  205.  
  206. Cameron Byrne
  207. T-Mobile USA
  208. Bellevue, WA
  209.  
  210.  
  211.  
  212.  
  213. Byrne Expires May 9, 2021 [Page 4]
  214.  
  215. Internet-Draft 64share-V2 November 2020
  216.  
  217.  
  218.  
  219.  
  220.  
RAW Paste Data