IPv6 Address Assignment to End-Sites
draft-palet-v6ops-rfc6177-bis-02
|
Document |
Type |
|
Active Internet-Draft (individual)
|
|
Last updated |
|
2018-10-09
|
|
Stream |
|
(None)
|
|
Intended RFC status |
|
(None)
|
|
Formats |
|
plain text
xml
pdf
html
bibtex
|
Stream |
Stream state |
|
(No stream defined) |
|
Consensus Boilerplate |
|
Unknown
|
|
RFC Editor Note |
|
(None)
|
IESG |
IESG state |
|
I-D Exists
|
|
Telechat date |
|
|
|
Responsible AD |
|
(None)
|
|
Send notices to |
|
(None)
|
IPv6 Operations (v6ops) J. Palet Martinez
Internet-Draft The IPv6 Company
Obsoletes: 6177 (if approved) L. Roberts
Intended status: Best Current Practice Stanford University, UIT
Expires: April 12, 2019 October 9, 2018
IPv6 Address Assignment to End-Sites
draft-palet-v6ops-rfc6177-bis-02
Abstract
The Regional Internet Registries (RIRs) policies have different views
regarding the recommendation of the prefix to be assigned to end-
sites. However, all them allow up to a /48 without further
justification and clearly state that the exact choice of how much
address space should be assigned to end-sites is a decision of each
operator.
This document reviews the architectural and operational
considerations of end-site assignments, and reiterates that
assignment policy and guidelines belong to the RIR community. This
revision is being made to emphasize that IPv6 protocol evolution
requires an ever-increasing availability of subnets at the end-site,
so policy should reflect that assignment of a single subnet is never
recommended.
This document obsoletes RFC6177 (IPv6 Address Assignment to End
Sites).
Status of This Memo
This Internet-Draft is submitted in full conformance with the
provisions of BCP 78 and BCP 79.
Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF). Note that other groups may also distribute
working documents as Internet-Drafts. The list of current Internet-
Drafts is at https://datatracker.ietf.org/drafts/current/.
Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet-Drafts as reference
material or to cite them other than as "work in progress."
This Internet-Draft will expire on April 12, 2019.
Palet Martinez & Roberts Expires April 12, 2019 [Page 1]
Internet-Draft IPv6 Address Assignment to End-Sites October 2018
Copyright Notice
Copyright (c) 2018 IETF Trust and the persons identified as the
document authors. All rights reserved.
This document is subject to BCP 78 and the IETF Trust's Legal
Provisions Relating to IETF Documents
(https://trustee.ietf.org/license-info) in effect on the date of
publication of this document. Please review these documents
carefully, as they describe your rights and restrictions with respect
to this document. Code Components extracted from this document must
include Simplified BSD License text as described in Section 4.e of
the Trust Legal Provisions and are provided without warranty as
described in the Simplified BSD License.
Table of Contents
1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 2
2. Considerations Regarding the Prefix Length . . . . . . . . . 4
3. On /48 Assignments to End-Sites . . . . . . . . . . . . . . . 5
4. Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
5. Security Considerations . . . . . . . . . . . . . . . . . . . 9
6. IANA Considerations . . . . . . . . . . . . . . . . . . . . . 9
7. Acknowledgements . . . . . . . . . . . . . . . . . . . . . . 9
8. Informative References . . . . . . . . . . . . . . . . . . . 9
Authors' Addresses . . . . . . . . . . . . . . . . . . . . . . . 11
1. Introduction
There are a number of considerations that factor into address and
prefix assignment policies. For example, to provide for the long-
term health and scalability of the public routing infrastructure, it
is important that prefixes aggregate well [Route-Scaling]. Likewise,
giving out an excessive amount of address space could result in
premature depletion of the address space. This document focuses on
the (narrower) question of what is an appropriate IPv6 address
assignment size for end-sites. That is, when end-sites request IPv6
address space from ISPs, what is an appropriate assignment size.
[RFC3177] called for a default end-site IPv6 assignment size of /48.
Subsequently, the Regional Internet Registries (RIRs) developed and
adopted IPv6 address assignment and allocation policies consistent
with ISP practices, and it triggered the development of [RFC6177].
Current RIR policies still allow using /48, but leave the decision in
the hands of the ISP. In some cases, encourage the assignment /48
blocks for all, while other RIRs encourage the assignment of smaller
(e.g., /56) blocks to residential end-sites, while keeping /48 for
business.
Palet Martinez & Roberts Expires April 12, 2019 [Page 2]
Internet-Draft IPv6 Address Assignment to End-Sites October 2018
More recently, a Global IPv6 Deployment Survey (for residential/
Show full document text