Re: [v6ops] Comments on draft-ali-ipv6rtr-reqs-02

Tim Chown <Tim.Chown@jisc.ac.uk> Tue, 04 April 2017 12:44 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 7D5511272E1 for <v6ops@ietfa.amsl.com>; Tue, 4 Apr 2017 05:44:26 -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 m_horHWuoFvQ for <v6ops@ietfa.amsl.com>; Tue, 4 Apr 2017 05:44:24 -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 15A6A127735 for <v6ops@ietf.org>; Tue, 4 Apr 2017 05:44:23 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=jisc.ac.uk; s=mimecast20170213; t=1491309862; bh=NN9+G+AFVe1pApdzlm7W+jQbk9iewYZCJlf7eHpQChs=; h=From:To:CC:Subject:Date:Message-ID:References:In-Reply-To:Content-ID:MIME-Version:Content-Type:Content-Transfer-Encoding; b=P9NgS3cJWYlVcISSGlfl2SVbULIgF1dRsZeabXggHHwRHT1xChewKC3L/cHZL4v5bEudZOZzQlR9BxxQjFsaVCXdnNm/8/KJGSi0w91WCMz+aj4FzfYM4t8Zz0g+44d44r3kZtL+wZYZP73xA4ez0FhC//czsJVN2B7Jf+oppm8=
Received: from EUR01-VE1-obe.outbound.protection.outlook.com (mail-ve1eur01lp0246.outbound.protection.outlook.com [213.199.154.246]) (Using TLS) by eu-smtp-1.mimecast.com with ESMTP id uk-mta-96-ReNwQQg8P0mlFHFavC6W6A-1; Tue, 04 Apr 2017 13:44:17 +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.1019.8; Tue, 4 Apr 2017 12:44:15 +0000
Received: from AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::29d9:4eb6:edcf:55dc]) by AM3PR07MB1140.eurprd07.prod.outlook.com ([fe80::29d9:4eb6:edcf:55dc%14]) with mapi id 15.01.1019.014; Tue, 4 Apr 2017 12:44:15 +0000
From: Tim Chown <Tim.Chown@jisc.ac.uk>
To: Russ White <7riw77@gmail.com>
CC: "v6ops@ietf.org" <v6ops@ietf.org>
Thread-Topic: [v6ops] Comments on draft-ali-ipv6rtr-reqs-02
Thread-Index: AQHSqLu/JAUmSx69OkO5wODN0Nb9M6GtflIAgAeyigA=
Date: Tue, 04 Apr 2017 12:44:15 +0000
Message-ID: <27A33147-2E96-438E-967C-C9A69B1F1AE6@jisc.ac.uk>
References: <AF63A18D-1734-48E1-B7D6-A707F080EC77@jisc.ac.uk> <01e701d2a967$e6021ef0$b2065cd0$@gmail.com>
In-Reply-To: <01e701d2a967$e6021ef0$b2065cd0$@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.3259)
x-ms-exchange-messagesentrepresentingtype: 1
x-originating-ip: [194.82.140.195]
x-microsoft-exchange-diagnostics: 1; AM3PR07MB1140; 7:4OE4cwMJWINpjWNd1YVFtoDhNwNF5f5dFZYtA0IY+PXfi9bwULzOmyS/mIdX5qyGNPSJ8/GDc/t1k2NFL2BYVpHb+Uog8PBNyCTm748Q6jtLz5zh2pXLxjgF4HIOPMQ9dnsnKgHIDn7vW7EK0pciqtM+4PwNGTb0kGGvcJXYm7Foi6vqTISkGcYjnYi9nwYjyB1pfs45YA+w/XIlbvqNF3AEydLa/uFRGEaUTbT33ilepmK3Tg9KNOnHwt8CUgR9N/rsJrXoHdG9icf+XSEdh94KnyU63ZbYW/C3y+t18lXYF4pAQ7rGv6uXTvYK3HnWutNijtB9ldUABG6zFob3SA==; 20:A3PCm/Seum57MGcoiSbswI9wnuSFa2efbepJkZImbRhZYBr3O8NEqUQC1JKRCaFBMTH9mChjiv8lwYN+GU4MTIBbxGLDFkpcXAOuJyh3Muk23F7T5Q6XnRPHDccpG9zbDfgUn6nPRBzOwK6Ruv2OpKiqBBJLb7iup8dJLN035nY=
x-ms-office365-filtering-correlation-id: b5c69b1c-9465-48e4-46a8-08d47b584dce
x-microsoft-antispam: UriScan:; BCL:0; PCL:0; RULEID:(22001)(2017030254075)(201703131423075)(201703031133081); SRVR:AM3PR07MB1140;
x-microsoft-antispam-prvs: <AM3PR07MB114095B5BECB23E8D20BEC66D60B0@AM3PR07MB1140.eurprd07.prod.outlook.com>
x-exchange-antispam-report-test: UriScan:;
x-exchange-antispam-report-cfa-test: BCL:0; PCL:0; RULEID:(6040450)(601004)(2401047)(8121501046)(5005006)(93006095)(93001095)(3002001)(10201501046)(6041248)(20161123562025)(20161123555025)(20161123564025)(201703131423075)(201702281529075)(201702281528075)(201703061421075)(20161123560025)(6072148); SRVR:AM3PR07MB1140; BCL:0; PCL:0; RULEID:; SRVR:AM3PR07MB1140;
x-forefront-prvs: 0267E514F9
x-forefront-antispam-report: SFV:NSPM; SFS:(10009020)(6009001)(39450400003)(39400400002)(39840400002)(39410400002)(24454002)(102836003)(3846002)(2950100002)(6116002)(42882006)(6916009)(305945005)(7736002)(82746002)(6436002)(3660700001)(2906002)(5250100002)(2900100001)(6486002)(6506006)(74482002)(230783001)(50986999)(76176999)(99286003)(8936002)(66066001)(53546009)(83716003)(6512007)(189998001)(86362001)(6246003)(57306001)(110136004)(1411001)(38730400002)(25786009)(50226002)(97736004)(36756003)(4326008)(8676002)(53936002)(81166006)(229853002)(33656002)(5660300001)(39060400002)(3280700002); DIR:OUT; SFP:1101; SCL:1; SRVR:AM3PR07MB1140; H:AM3PR07MB1140.eurprd07.prod.outlook.com; FPR:; SPF:None; MLV:ovrnspm; PTR:InfoNoRecords; LANG:en;
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-ID: <EF7A66308DED9543849C9ACCA79BFE92@eurprd07.prod.outlook.com>
MIME-Version: 1.0
X-OriginatorOrg: jisc.ac.uk
X-MS-Exchange-CrossTenant-originalarrivaltime: 04 Apr 2017 12:44:15.7043 (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: ReNwQQg8P0mlFHFavC6W6A-1
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/_AYhYDc0s2JmVDbMhRX-CTzAiaM>
Subject: Re: [v6ops] Comments on draft-ali-ipv6rtr-reqs-02
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: Tue, 04 Apr 2017 12:44:26 -0000

Hi,

> On 30 Mar 2017, at 16:11, Russ White <7riw77@gmail.com> wrote:
> 
> 
>> Overall, a very nicely written document. The intro sections are particularly
>> good to read.
> 
> Thanks!
> 
>> I suggest adding sections in the draft on:
>> a) MLDv2 - personally I’d like to see a MUST for MLDv2 support
>> b) RFC8106 support - make RDNSS option support in RAs a MUST
> 
> I will take a look at these -- I think they would be good to add, just have to scare up some text around them.

In 6man, there was support for MLDv2 being a MUST (noting the issues caused by a single MLDv1-only host on a subnet).

But you’ve seen the 140 (and counting) emails on RDNSS and RAs in v6ops :)  Whatever comes of that, we should be consistent in the two drafts we’re editing.

>> And also review the wording on SLAAC in Section 3.3.
>> a) Change SLAAC being enabled by default from a SHOULD to a MUST
> 
> This is mostly a result of my not knowing what to do here, so I went with the "gentler" requirement. I'm happier with MUST here if the community agrees.

I think there have been a couple of other supporting comments on this. I guess if you change it you’ll find out who squeals.

>> b) Probably good to distinguish SLAAC for LLs and SLAAC for globals; RFC6434
>> says routers MUST be able to generate LL addresses; the draft currently only
>> says SHOULD; I’d make that a MUST.
> 
> Okay.
> 
>> c) RFC4862 says DAD is a MUST, in the draft it’s currently only a SHOULD; is
>> there a reason for it not to be a MUST?
> 
> Nope -- again, I'm just sometimes overcautious. I can change this to a MUST.

It would be good to be compliant with RFC4862, unless there’s a good reason not to be.

>> The only significant “clash” with RFC6434-bis (which is in 6net tomorrow) is
>> the section 3 text; the rest syncs pretty well as it is, which is good news.
> 
> I'll take a look at this to see where we might clash, and try to get those bits worked out.

Overall, there’s minimal overlap - mainly section 3 as above.

Tim

> 
> 😊 /r
>