Re: [v6ops] draft-palet-v6ops-rfc6177-bis
Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 28 August 2018 05:11 UTC
Return-Path: <brian.e.carpenter@gmail.com>
X-Original-To: v6ops@ietfa.amsl.com
Delivered-To: v6ops@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 006B6130DC6 for <v6ops@ietfa.amsl.com>; Mon, 27 Aug 2018 22:11:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_NONE=-0.0001, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id UEe3YI3B6rJS for <v6ops@ietfa.amsl.com>; Mon, 27 Aug 2018 22:11:29 -0700 (PDT)
Received: from mail-pf1-x431.google.com (mail-pf1-x431.google.com [IPv6:2607:f8b0:4864:20::431]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 0032F124D68 for <v6ops@ietf.org>; Mon, 27 Aug 2018 22:11:28 -0700 (PDT)
Received: by mail-pf1-x431.google.com with SMTP id d4-v6so210465pfn.0 for <v6ops@ietf.org>; Mon, 27 Aug 2018 22:11:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:references:from:organization:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ld9VXxtW0l5Ce22HOXnlI5L23knDMW2POsNeANsTpUE=; b=Jl4O7dURMHAD5e10C48lZcS0tpbH08RbZhY+D2s0yAUoFJxI5/iIqPJok7vwBcpdtm 1HrgDnsvH+cL5RkUbPEzgZwOzwvd/IQ0JcU+gcwZRmXvskwxJU0r7CEBoUK6iAZBlu59 pQNnlohEC56cFEPxtcF+t20xDnpcilvuopSMqbge8BcUqyUx5pWXlFbTWUyGMPcURaM5 /XJ//ta2q0T8tD0vFH90fPKT+pRRuCIUluYikh5IOhkllrBuk/dMW5AS2djGyknZrQ7B siw/BtVR0IHV1VSfj+LBH3H1oBiQ1BK9bVaDRn8TNiXwO6dBp7wFm87kYZ8Dlo0y8nK2 5xqA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:references:from:organization :message-id:date:user-agent:mime-version:in-reply-to :content-language:content-transfer-encoding; bh=ld9VXxtW0l5Ce22HOXnlI5L23knDMW2POsNeANsTpUE=; b=B9hXLjWY2kBk9C5x16GmdssYBs/U9gwlNjFfI2itxa6+zBLGoO7QIGQ3ZRVulGL382 x04IrCNpOl58Z9FKZUJRCoP4q+RRKFo5+tMDTtwgtY3jBALapnDS38b5d8xpF1VXrGNb 49Q9MinvDhIp4b7+EGzsFRcjfyNmTDD9QjuDSLI76DZq4YC+R4fs9Staw68WnHXkNouS k2bfQffxdmQLKwwrjizG5Ku7yZ49E/h+DJ8o5FW4ExqkiffAYmuIfCt7uVM9RDjMAmd6 Cv3iL3+yhCq2XLqmPeIoqELGqr3wsPfremOy87uPfEw6BQ0Kcd97bt0YzpZ3827uVtoS wzRw==
X-Gm-Message-State: APzg51CR2zH0xtlcPo0zzfgDRTPAxrSoitstDvSOjtSoxy2c7+mQtJw/ LRZpTn+gVSMVE0p9cHi8uXGX8z8u
X-Google-Smtp-Source: ANB0Vdbu+o3qfJdv5XPsP4+r1urC4gWySA1NbeEpBnIpA9eFDgUh51ugZ1nEhcsN2CBnH7U7TgOERg==
X-Received: by 2002:a62:5d89:: with SMTP id n9-v6mr17276487pfj.102.1535433088147; Mon, 27 Aug 2018 22:11:28 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.68.33]) by smtp.gmail.com with ESMTPSA id u83-v6sm476559pfj.37.2018.08.27.22.11.25 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 27 Aug 2018 22:11:27 -0700 (PDT)
To: Ron Bonica <rbonica@juniper.net>, "v6ops@ietf.org" <v6ops@ietf.org>
References: <CO1PR05MB443BFFA74AAEB374E38BD8FAE0B0@CO1PR05MB443.namprd05.prod.outlook.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Organization: University of Auckland
Message-ID: <80ec965c-4a6c-3cc8-b92f-ad03603f9223@gmail.com>
Date: Tue, 28 Aug 2018 17:11:23 +1200
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1
MIME-Version: 1.0
In-Reply-To: <CO1PR05MB443BFFA74AAEB374E38BD8FAE0B0@CO1PR05MB443.namprd05.prod.outlook.com>
Content-Type: text/plain; charset="utf-8"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/-bVEIe_irUT1k_ryKC0QV_8oURY>
Subject: Re: [v6ops] draft-palet-v6ops-rfc6177-bis
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.27
Precedence: list
List-Id: v6ops discussion list <v6ops.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/v6ops>, <mailto:v6ops-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/v6ops/>
List-Post: <mailto:v6ops@ietf.org>
List-Help: <mailto:v6ops-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/v6ops>, <mailto:v6ops-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 28 Aug 2018 05:11:31 -0000
Hi, I fully support this draft. Here are a few (minor) wording issues and some nits. Issues: ------- > [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 those recommendations, and it triggered the development of > [RFC6177]. However, some of the RIRs, have later on updated those > policies, which still allow using /48, but leave the decision in the > hands of the ISP, or even, in some cases, encourage the assignment of > smaller (e.g., /56) blocks to residential end-sites, while keeping > /48 for business. I don't think that is accurate. Actually there was push-back *from* the RIRs against the wording of 3177, because some ISPs did not wish to be consistent with it. Here's another version: [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 this triggered the development of [RFC6177]. Current RIR policies still allow using /48, but leave the decision in the hands of the ISP, or even, in some cases, endorse the assignment of smaller (e.g., /56) blocks to residential end-sites, while keeping /48 for business. > This raises the question of a possible misinterpretation of [RFC6177] > by at least 1/3rd of the operational community and consequently, the > need to revisit it. No, I don't think there's any misinterpretation. I think it's quite clear (as in my previous comment) that this is exactly why the ISP community pushed for RFC6177. I think we should phrase this a bit differently. This raises the question of over-zealous interpretation of [RFC6177] by at least one third of the ISP community and consequently, the need to revisit it. > It might be tempting to give home sites a single /64, since that is > already significantly more address space compared with today's IPv4 > practice. However, this precludes the certainty that even home sites > will grow to support multiple subnets going forward. Hence, it is > strongly intended that even home sites be given a big number of > subnets worth of space, by default. Hence, this document still > recommends giving home sites significantly many more than a single > /64. I think a reference to RFC7368 and RFC7788 would be useful here, to make it clear that this is not guesswork. (Note that HNCP is mentioned later, so there is a little repetition in the argument.) Nits: ----- > Abstract > > The Regional Internet Registries (RIRs) policies, have different Delete the comma > requires an ever-increasing availability of subnets at the end-site > and so, policy should reflect that assignment of a single subnet is NEW requires an ever-increasing availability of subnets at the end-site, so policy should reflect that the assignment of a single subnet is I see a number of other minor syntax and punctuation nits in the text, but I'm afraid I'm going to leave those for the copy-editor. Regards, Brian
- [v6ops] draft-palet-v6ops-rfc6177-bis Ron Bonica
- Re: [v6ops] draft-palet-v6ops-rfc6177-bis Brian E Carpenter
- Re: [v6ops] draft-palet-v6ops-rfc6177-bis Mudric, Dusan (Dusan)
- Re: [v6ops] draft-palet-v6ops-rfc6177-bis Rajiv Asati (rajiva)
- Re: [v6ops] draft-palet-v6ops-rfc6177-bis JORDI PALET MARTINEZ