Re: [v6ops] draft-palet-v6ops-rfc6177-bis

"Mudric, Dusan (Dusan)" <dmudric@avaya.com> Tue, 28 August 2018 15:12 UTC

Return-Path: <dmudric@avaya.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 1D175130DE5 for <v6ops@ietfa.amsl.com>; Tue, 28 Aug 2018 08:12:53 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.899
X-Spam-Level:
X-Spam-Status: No, score=-6.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
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 dWVpGtQQWzbS for <v6ops@ietfa.amsl.com>; Tue, 28 Aug 2018 08:12:51 -0700 (PDT)
Received: from co300216-co-outbound.net.avaya.com (co300216-co-outbound.net.avaya.com [198.152.13.100]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3F6A4130DD9 for <v6ops@ietf.org>; Tue, 28 Aug 2018 08:12:51 -0700 (PDT)
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A2HwAADTZYVb/wUHmMZaGQEBAQEBAQEBAQEBAQcBAQEBAYJ6VWV/KAqYIoINl2U7CyMJAoQ+AoJ1ITgUAQIBAQEBAQECAgJpHAyCaC8BAQQHAwwvCQIDAQEBAQEBAU8CD0cBARgBAQEBAgESKDQQBwQCAQgNBAQBAQsUEDIdCAEBBAESCAwOgwCBeQgBDplFix0aAopBBYlWF4FCPoESRoJMgxsEGIFJgzCCJgKbLAkChjGJU4haA4Vsix2ILIFYIoFScBU7gmmCJReDRYpSb4EWimsBgRsBAQ
X-IPAS-Result: A2HwAADTZYVb/wUHmMZaGQEBAQEBAQEBAQEBAQcBAQEBAYJ6VWV/KAqYIoINl2U7CyMJAoQ+AoJ1ITgUAQIBAQEBAQECAgJpHAyCaC8BAQQHAwwvCQIDAQEBAQEBAU8CD0cBARgBAQEBAgESKDQQBwQCAQgNBAQBAQsUEDIdCAEBBAESCAwOgwCBeQgBDplFix0aAopBBYlWF4FCPoESRoJMgxsEGIFJgzCCJgKbLAkChjGJU4haA4Vsix2ILIFYIoFScBU7gmmCJReDRYpSb4EWimsBgRsBAQ
X-IronPort-AV: E=Sophos;i="5.53,299,1531800000"; d="scan'208";a="295459632"
Received: from unknown (HELO co300216-co-erhwest.avaya.com) ([198.152.7.5]) by co300216-co-outbound.net.avaya.com with ESMTP; 28 Aug 2018 11:12:49 -0400
X-OutboundMail_SMTP: 1
Received: from unknown (HELO AZ-US1EXHC04.global.avaya.com) ([135.11.85.15]) by co300216-co-erhwest-out.avaya.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 28 Aug 2018 11:12:48 -0400
Received: from AZ-US1EXMB03.global.avaya.com ([fe80::a5d3:ad50:5be9:1922]) by AZ-US1EXHC04.global.avaya.com ([135.11.85.15]) with mapi id 14.03.0382.000; Tue, 28 Aug 2018 11:12:47 -0400
From: "Mudric, Dusan (Dusan)" <dmudric@avaya.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>, Ron Bonica <rbonica@juniper.net>, "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] draft-palet-v6ops-rfc6177-bis
Thread-Index: AdQ+ERSkgrY6L5QoTzWBeUJlAjTblQAngKOAAAyJdZA=
Date: Tue, 28 Aug 2018 15:12:46 +0000
Message-ID: <9142206A0C5BF24CB22755C8EC422E459CB44EA3@AZ-US1EXMB03.global.avaya.com>
References: <CO1PR05MB443BFFA74AAEB374E38BD8FAE0B0@CO1PR05MB443.namprd05.prod.outlook.com> <80ec965c-4a6c-3cc8-b92f-ad03603f9223@gmail.com>
In-Reply-To: <80ec965c-4a6c-3cc8-b92f-ad03603f9223@gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [135.11.85.50]
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/KXwLRdQR95xgAodhwiT1mrtQres>
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 15:12:53 -0000

>    Current RIR policies still allow using /48, but leave the decision in the
>    hands of the ISP

Decision like this should not be in anybody's hands. /48 should be given automatically, when needed.

Dusan

> -----Original Message-----
> From: v6ops <v6ops-bounces@ietf.org> On Behalf Of Brian E Carpenter
> Sent: Tuesday, August 28, 2018 1:11 AM
> To: Ron Bonica <rbonica@juniper.net>; v6ops@ietf.org
> Subject: Re: [v6ops] draft-palet-v6ops-rfc6177-bis
> 
> 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 mailing list
> v6ops@ietf.org
> https://urldefense.proofpoint.com/v2/url?u=https-
> 3A__www.ietf.org_mailman_listinfo_v6ops&d=DwICAg&c=BFpWQw8bsuKpl
> 1SgiZH64Q&r=UT3Bk9cbLeaJxhf3iCrhIoUWB8YLZU23029sMQGQ2kY&m=Yd3D
> j3oVG2HTAJSudmciO1QwxdBm5v8tty3i7nRVEE8&s=MyBUglnUbBkNpooKN-
> YKnbJrsKVzg92HOWY-ZK_4RMU&e=