IETF Logo Mail Archive

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

Mikael Abrahamsson <swmike@swm.pp.se> Fri, 21 April 2017 13:54 UTC

Return-Path: <swmike@swm.pp.se>
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 13407128C81 for <v6ops@ietfa.amsl.com>; Fri, 21 Apr 2017 06:54:24 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.301
X-Spam-Level:
X-Spam-Status: No, score=-4.301 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, RP_MATCHES_RCVD=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=swm.pp.se
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 7bK66z82yV0Q for <v6ops@ietfa.amsl.com>; Fri, 21 Apr 2017 06:54:22 -0700 (PDT)
Received: from uplift.swm.pp.se (ipv6.swm.pp.se [IPv6:2a00:801::f]) (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 0D459120227 for <v6ops@ietf.org>; Fri, 21 Apr 2017 06:54:22 -0700 (PDT)
Received: by uplift.swm.pp.se (Postfix, from userid 501) id E3125AD; Fri, 21 Apr 2017 15:54:19 +0200 (CEST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=swm.pp.se; s=mail; t=1492782859; bh=FVoY53t5Dh6oy8hHKNz/ojUS+jKxHpUk69DG/g5eyKo=; h=Date:From:To:Subject:In-Reply-To:References:From; b=22HNn/hGvMMGQyz/1eDEhcXsniOB4lu0SUm30ndN/DiDjf8M39Q7flxq76CLpNYcs 9SffIhSYji2N37K6yG9OoLvp5lCqTrsKdW952bLZTeRHoaVK9now19UnI/v/+KzQhY BRUz70Tq88QbJFW4HDwRUioEVIOOXYdNPQ3zM/FM=
Received: from localhost (localhost [127.0.0.1]) by uplift.swm.pp.se (Postfix) with ESMTP id E0785A6 for <v6ops@ietf.org>; Fri, 21 Apr 2017 15:54:19 +0200 (CEST)
Date: Fri, 21 Apr 2017 15:54:19 +0200
From: Mikael Abrahamsson <swmike@swm.pp.se>
To: IPv6 Ops WG <v6ops@ietf.org>
In-Reply-To: <BLUPR0501MB20513F21FE599ED243BA9AAFAE3C0@BLUPR0501MB2051.namprd05.prod.outlook.com>
Message-ID: <alpine.DEB.2.02.1704211545060.5591@uplift.swm.pp.se>
References: <BLUPR0501MB20513F21FE599ED243BA9AAFAE3C0@BLUPR0501MB2051.namprd05.prod.outlook.com>
User-Agent: Alpine 2.02 (DEB 1266 2009-07-14)
Organization: People's Front Against WWW
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset="US-ASCII"; format="flowed"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/To0wPLcTBAhtbPy35AcFAemg9xc>
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: Fri, 21 Apr 2017 13:54:24 -0000

On Wed, 22 Mar 2017, Ron Bonica wrote:

> 3) The title of Section 5.3 is "Maximum Transmission Unit and Jumbo 
> Frames". However, there is no further mention of Jumbo Frames. Could we 
> explore Jumbo's possibly with an eye towards deprecation.

I am strongly in favour of support of jumbo frames.

I would like to see the document specify an L3 MTU of 9180 as its SHOULD 
requirement. All major core router vendor supports this today. The reason 
for 9180 is that this is what RFC2225, RFC2492, RFC1209 mention.

Other comments:

3.3 It would be good if the draft referenced for instance RFC8071 for 
Netconf-call-home and draft-ietf-netconf-zerotouch-13 for zerotouch 
plug'n'play provisioning.

5.4. The ICMP ECHO/REPLY requirement here opposes what's in RFC4890. I 
prefer what RFC4890 says.

-- 
Mikael Abrahamsson    email: swmike@swm.pp.se

v2.23.0 | Report a Bug | By Email