Re: [v6ops] I-D Action: draft-palet-v6ops-rfc6177-bis-00.txt

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 29 August 2018 22:29 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 8DD9D130DEA; Wed, 29 Aug 2018 15:29:23 -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=unavailable 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 T98Alu2TIveE; Wed, 29 Aug 2018 15:29:21 -0700 (PDT)
Received: from mail-pg1-x52f.google.com (mail-pg1-x52f.google.com [IPv6:2607:f8b0:4864:20::52f]) (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 2AD0C130DE9; Wed, 29 Aug 2018 15:29:21 -0700 (PDT)
Received: by mail-pg1-x52f.google.com with SMTP id a13-v6so249218pgt.7; Wed, 29 Aug 2018 15:29:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=subject:to:cc:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=ayI5Tq6tNu4xpDxYnSPEcEK0QWZbaahfJYiDxDSW4xA=; b=ZpdsV7vbhcNx1b71Oi6vEFFEAZ/zzeelWmij9tR+SZWUkNlNKIePeqXcVaWhi8Hur6 cV9E1eOLskNxpT8TC625Qwh2cqxDNuYeGv5K5sxtcfLluN5OnwO5Uc9IzXbpjsL8jIJw MmWliKwnOqbDN0vGhQtDKJBaCzd/AG+sJntiUoTKEdLLsKeoDRUcp7AvMHLFGI+qYpGw U6TOHvrcJd8VNmEtaOt0UdanQn5VOA2bgQgD4FKOrmQKjhFwWfQntR5/Ga4xqNieQGka 65ZXA1TS9S41km0TyD4s0PF6X5oFMH6Ifmrb2Z2oCa44j8a7j0qwyZEbMEMyLb3eUf/C NkEg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=ayI5Tq6tNu4xpDxYnSPEcEK0QWZbaahfJYiDxDSW4xA=; b=jVE9k16bGw4Wl5N5hx5k8FYll2KJTfYiVcpO2C1TQiCzW/BcgI9fMD9QgNhT2FPXYb Xid6wbBRJmQHShAwHcbahhJU1Fuvv/zU+B6UYvO5BTvi6nF6cZWSyrfuLFudSHRDkKZl 3kB2NmzClvh11k+rqY8VVtFlH3mBGUW/Jhob2RzXC28Ne7nFrag+l9BHDQ0PyiD349PG Q9l+QtiCqbT4VAnH87Sq3+8FOU1gXS+uR2FiPBJOR2lKo9Vm0pea/Wp+JcpLOu15pT3P sYgb1IQjOxKf2D4KL/6hXi/cXX5/hVT262r3hKyKn/KaLDfEcgSnLb0A9jXvciLw6nXr aWTQ==
X-Gm-Message-State: APzg51D/TEUYTVBGICFj0rESyToj01VQDJWwIlQ+J/7KCAN21PsShAg4 sR1wsBJInjWZD5dn5BuLrpI=
X-Google-Smtp-Source: ANB0VdYZOwxNRBS/R90SwEGfnC4WO0i7u4e5CtBi9m/K4fFDzJ1uEfI09ke434ttPL7qkMCFTwD9cg==
X-Received: by 2002:a63:1021:: with SMTP id f33-v6mr7235720pgl.72.1535581760608; Wed, 29 Aug 2018 15:29:20 -0700 (PDT)
Received: from [192.168.178.30] ([118.148.68.33]) by smtp.gmail.com with ESMTPSA id k69-v6sm8237775pgd.9.2018.08.29.15.29.17 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 29 Aug 2018 15:29:19 -0700 (PDT)
To: "STARK, BARBARA H" <bs7652@att.com>, 'Fred Baker' <fredbaker.ietf@gmail.com>, "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
Cc: "draft-palet-v6ops-rfc6177-bis@ietf.org" <draft-palet-v6ops-rfc6177-bis@ietf.org>, IPv6 Operations <v6ops@ietf.org>, JORDI PALET MARTINEZ <jordi.palet=40consulintel.es@dmarc.ietf.org>
References: <153017691583.14743.17000446834856511528@ietfa.amsl.com> <78a36a81-3bb3-9d47-aa06-8da8f7594677@gmail.com> <C040E02F-7BEC-4FF9-8585-BE380B6859DE@consulintel.es> <alpine.DEB.2.02.1807191054090.7979@networking.stanford.edu> <9142206A0C5BF24CB22755C8EC422E459CB44344@AZ-US1EXMB03.global.avaya.com> <f1bc1848-abe0-553e-0fdf-623eb0d1a871@gmail.com> <9142206A0C5BF24CB22755C8EC422E459CB44E7E@AZ-US1EXMB03.global.avaya.com> <A82D3E92-C68D-4685-BD3D-6B2656F9A8A6@gmail.com> <2D09D61DDFA73D4C884805CC7865E6114DE872CA@GAALPA1MSGUSRBF.ITServices.sbc.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <e4ac2192-e18b-9d64-c33a-79523d642e1d@gmail.com>
Date: Thu, 30 Aug 2018 10:29:15 +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: <2D09D61DDFA73D4C884805CC7865E6114DE872CA@GAALPA1MSGUSRBF.ITServices.sbc.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/yo4EF4Bbxiy2GTMJ7VQf6CDmZrc>
Subject: Re: [v6ops] I-D Action: draft-palet-v6ops-rfc6177-bis-00.txt
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: Wed, 29 Aug 2018 22:29:24 -0000

Barbara,
On 2018-08-30 00:11, STARK, BARBARA H wrote:
>> My understanding, no hats and potentially incorrect, is that any ISP I know of
>> will respond to a DHCPv6 IA_PD with a prefix at least as large as requested,
>> up to /48.
> 
> I don't think this is correct. Of course, any provider using 6rd won't respond to DHCPv6 at all. I'm aware of a lot of 6rd out there.
> Wireless LTE providers don't tend to support DHCPv6, either. The /64 advertised by the RA in an LTE environment is all the LTE UE will get. That includes the case where the LTE UE is supporting a fixed wireless installation.
> For ISPs that support DHCPv6, it may or may not be the case. I've heard several say they do, but I'm not aware of a survey of all ISPs that would tell me how prevalent it is.
> 
> BTW, I disagree with the abstract's statement that the "policy should reflect that assignment of a single subnet is never appropriate." I do not believe this takes into consideration the fact that it would be tremendously expensive for some ISPs to replace their current equipment when those current equipment vendors are being slow about supporting certain features. Cost is always an appropriate consideration. 

I disagree. Yes, of course cost is always a consideration, but that doesn't
make a lower case "should" inappropriate.

> It also does not take into account CE routers that only request a single /64. 

That's irrelevant. The customer might have bought such a router, but the
next customer along might have bought a full homenet-supporting CE.

> I think it's inappropriate for IETF to be trying to dictate what is and isn't "appropriate". Recommending a best current practice is fine. But that's not the same as saying something is "never appropriate".

Let's say "never recommended" then.

   Brian