Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-00.txt

Tim Chown <Tim.Chown@jisc.ac.uk> Mon, 08 May 2017 10:32 UTC

Return-Path: <tim.chown@jisc.ac.uk>
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 55CFE129423 for <v6ops@ietfa.amsl.com>; Mon, 8 May 2017 03:32:28 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.321
X-Spam-Level:
X-Spam-Status: No, score=-4.321 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=jisc.ac.uk
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 cSkXySpy5cQj for <v6ops@ietfa.amsl.com>; Mon, 8 May 2017 03:32:26 -0700 (PDT)
Received: from eu-smtp-delivery-189.mimecast.com (eu-smtp-delivery-189.mimecast.com [207.82.80.189]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E1E3D1293D6 for <v6ops@ietf.org>; Mon, 8 May 2017 03:32:25 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1494239544; bh=Z8lZ/BGYXGGemunpMVnA/7grHJLDDbXwIivpo5hrf2k=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=E0KIWZ1KWjpgLbJzlNXhwcGRaXr0NAqq93jVTBO50xGNsZk7+DQpICQcu5RNMd576LEvzJ2SwJn1SLmOYkLHiJRhe/OhDL8sC5H3Hnl46CSQJsKuIMrl7unf5wOyUB1UDjI9a9gg0AMQ5v8kn1W48BTQPkQv1nuaEbr0ETba0sY=
Received: from EUR01-HE1-obe.outbound.protection.outlook.com (mail-he1eur01lp0209.outbound.protection.outlook.com [213.199.154.209]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-64--nuCjy-nNf2v3rJ747e5Zg-1; Mon, 08 May 2017 11:32:20 +0100
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) by AM3PR07MB1140.eurprd07.prod.outlook.com (10.163.188.14) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1084.7; Mon, 8 May 2017 10:32:18 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::cc2e:e06e:e272:6d7a]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::cc2e:e06e:e272:6d7a%15]) with mapi id 15.01.1084.015; Mon, 8 May 2017 10:32:18 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Lorenzo Colitti <lorenzo@google.com>
CC: "v6ops@ietf.org WG" <v6ops@ietf.org>
Thread-Topic: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-00.txt
Thread-Index: AQHSxetDwSE+lEBW30O41GjofsWp46HptMcAgACMJoA=
Date: Mon, 08 May 2017 10:32:18 +0000
Message-ID: <DAD58E18-E6DE-4887-8F3D-27CCA9011187@jisc.ac.uk>
References: <149402169430.8512.11192508581005769547@ietfa.amsl.com> <CAKD1Yr2Z=HrLyS5578fZ5s5Qnaf+aT=A_O3D-+9FKXOzsFPxZA@mail.gmail.com>
In-Reply-To: <CAKD1Yr2Z=HrLyS5578fZ5s5Qnaf+aT=A_O3D-+9FKXOzsFPxZA@mail.gmail.com>
Accept-Language: en-GB, en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-mailer: Apple Mail (2.3273)
x-originating-ip: [2001:a88:d510:1101:e966:38a8:dbd6:9e99]
x-ms-publictraffictype: Email
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1140; 7:PLHwSSkGLMcgfwNoNBXhgnohjLkKqOxtPJBW1O6evJPkkRcbO+ZUPhhS33hCc4AFDjawXU9QrWdIaYsX4udwaVLjSDwujTQNQXoc01YZENj2cLP3dFnZ55Rh3PnxjFa+C7JwfyViPuHRr7sKggSocdo+3nFTp0QJbbAEGGKIS+Ie7RhzmhTi1x1OAxVZ0BncE6HMDXLjLuQ5UBjkUBQo/ONBBjQCJsPT/A+cbppqEhpGEJ8GiY8035+G+D5EeJ09PptmLlXLqoLasqPqrv3cPqo2Os7ZrMwfBOl+sF03GMxW/WQn466D5W2zI8sUFJ8iMgLIm1gTgywWwt/wHaAK1A==; 20:EejyofVep8OwPm+8Lmogg2nlXGmJoFywiveKSL+mqiXostPVnNpbGxSRF+rgxsFQ2lt1wanXuhLYPRk3bq7VZYxjWT6VhPOMHAlrp37bNg7FZfNMyd2Uznp5M4iBRi13WQxTOwbPgnSbgZiDplwO6wqO/WklJha1t9/29fWmkcM=
x-ms-office365-filtering-correlation-id: b3471678-bd85-4812-f949-08d495fd80ae
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:AM3PR07MB1140;
x-microsoft-antispam-prvs: <AM3PR07MB114044B7B105B6573DBBF4C0D6EE0@AM3PR07MB1140.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:(158342451672863)(211936372134217);
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(10201501046)(93006095)(93001095)(3002001)(6041248)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(201703061406153)(20161123560025)(20161123562025)(20161123555025)(20161123564025)(20161123558100)(6072148); SRVR:AM3PR07MB1140; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1140;
x-forefront-prvs: 0301360BF5
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39410400002)(39400400002)(39450400003)(39840400002)(24454002)(377454003)(110136004)(3280700002)(5660300001)(25786009)(3660700001)(6246003)(86362001)(38730400002)(53546009)(33656002)(5250100002)(36756003)(4326008)(81166006)(8936002)(2906002)(230783001)(8676002)(50226002)(2950100002)(6512007)(478600001)(6916009)(6486002)(189998001)(99286003)(305945005)(74482002)(82746002)(7736002)(83716003)(6506006)(229853002)(6436002)(50986999)(53936002)(76176999)(102836003)(6116002)(42882006); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1140; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:sfv; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <0AB27719B625C54B806D803A52E5DB83@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 08 May 2017 10:32:18.3016 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 48f9394d-8a14-4d27-82a6-f35f12361205
X-MS-Exchange-Transport-CrossTenantHeadersStamped: AM3PR07MB1140
X-MC-Unique: -nuCjy-nNf2v3rJ747e5Zg-1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Gep3KYbYDw53KVdZGucmB_3dIIU>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.22
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: Mon, 08 May 2017 10:32:28 -0000

Hi,

> On 8 May 2017, at 03:10, Lorenzo Colitti <lorenzo@google.com> wrote:
> 
> On Sat, May 6, 2017 at 7:01 AM, <internet-drafts@ietf.org> wrote:
>         Title           : Requirements for IPv6 Routers
>         Authors         : Zaid Ali Kahn
>                           John Brzozowski
>                           Russ White
>         Filename        : draft-ietf-v6ops-ipv6rtr-reqs-00.txt
> 
> As Ted has stated many times, this text:
> 
> ======
>  Routers supporting IPv6, and intended for user facing
>    connections, MUST support:
> 
>    o  [RFC3646]: DNS Configuration options for Dynamic Host
>       Configuration Protocol for IPv6 (DHCPv6).
> ======
> 
> needs clarification. Does it mean that:
> 	• A router MUST contain a stateless DHCPv6 server implementation that supports the DNS option?
> 	• A router MUST contain a DHCPv6 relay implementation that supports the DNS option?
> 	• If a router contains an DHCPv6 server or relay implementation, then that implementation supports the DNS option?
> #1 or #2 would be a change to the IPv6 node requirements, which say:
> 
> ====
>    support for DHCP
>    server functionality on routers is optional.  However, routers
>    targeted for deployment within more complex scenarios (as described
>    above) SHOULD support relay agent functionality
> ====
> 
> I don't think it makes sense to say #1 or #2 and thus say that all IPv6 routers MUST support DHCPv6, because:
> 	• Other than for home gateways where DHCPv6 is required, I'd expect that the vast majority of routers don't actually support it at all (at least not in all feature sets).
> 	• In most places in the network there's not even any point in supporting it, because it will never be used. DHCPv6 can only ever be used in routers that serve as first-hop routers for hosts, so a backbone router will never need a DHCPv6 server or relay.
> #3 does make sense.

Worth noting that the node requirements document is undergoing an update, so its text might change.

I would certainly say that #3 is a minimum

There are also of course enterprises that wish to run DHCPv6, but I’d assume they would do so using first-hop relays. In that light, adding at least a SHOULD for RFC6939 would be good, if its not in this draft already. 

The text should probably talk about DHCPv6 requirements for routers that may typically be deployed in client-facing scenarios.

Tim