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

Brian E Carpenter <brian.e.carpenter@gmail.com> Wed, 21 March 2018 19:03 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 4FC43127201 for <v6ops@ietfa.amsl.com>; Wed, 21 Mar 2018 12:03:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 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, URIBL_BLOCKED=0.001] autolearn=ham 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 1AEQ37uChgxt for <v6ops@ietfa.amsl.com>; Wed, 21 Mar 2018 12:03:03 -0700 (PDT)
Received: from mail-pg0-x22e.google.com (mail-pg0-x22e.google.com [IPv6:2607:f8b0:400e:c05::22e]) (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 9694A12E050 for <v6ops@ietf.org>; Wed, 21 Mar 2018 12:03:03 -0700 (PDT)
Received: by mail-pg0-x22e.google.com with SMTP id t12so527806pgp.13 for <v6ops@ietf.org>; Wed, 21 Mar 2018 12:03:03 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=sender:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=p/GraLQ5vEGQORAIJ62A1ilYNDsbeVi+ijqMZ+xdoA0=; b=jRonxPrPjCwSlsj5ipiY2jTg/VqDZbUg6j9vVXqWgn5ccHe4VKQGbM6P7Yj9UlZ1K3 DaGKdFIOL9VVMYcI/sY7VDj9je5y4y1CTGGnNVHiXmmPzWmtkZaROfvH7ze/WZx9gVRD 2hAR3/GY4UcC5CCSnt2twCQfFuq66nKxRE4D5q+pMs1u11CPpd1iFqmsabsOUOKx4YpG IpTplB1h7eRaNTApFjUJjkgLy+/PRc2YGaI9tjPFiSj5URU3BLx5Zk/HcDAr47ujJyzV I/7nBeoKG+ERLsZk+lhxiybuY1D0VWErchdheLBBL254+rGLCUdBVDOjivyAtG5RXLMW Hbvg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:sender:subject:to:references:from:message-id :date:user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=p/GraLQ5vEGQORAIJ62A1ilYNDsbeVi+ijqMZ+xdoA0=; b=l8rkvhJXSgrr5XfhqKSBnnwZR03CTvscdDGQylrrATBhUx6NBky4AbzLFDgjRfoAPl 1hjixfnVOSgmRMX6OCZlL/1MPXvBIQKrlHVtMN7U5SKemfUFPHY3SgvhiV45qQ7y9gSN HgK6jjyCrvcAjoQLgCawCvxPqI3k2rDqqtvC+SAdniN/L0R5oH6skSErvoiBMCx/oSDn yNnMngaKbXSfIwW5fB5f+gX7yIPCtZWc7o3a8YshjGMmZaZA8E+Xtm3F8BpYP3RtGNkB nteSvRVzsNZ4qrMPMW/fjaY4t78HkLAnOA7RGB60OhcdY1LZLaIlbZ1KDagqsxonlT9J yWYQ==
X-Gm-Message-State: AElRT7H6tCr2lKY/uME4qrwOPHsDJVJ7czvStsR/uIdq3cVgltdvxs25 gAAuR5D/5eagNhHwlv6uSGNKcQ==
X-Google-Smtp-Source: AG47ELuDSpwklWQcCT/dA02TCxP8eP4zD0IJztPhxQZVOBn02W74ALorCLh6y4ZFUZYKd4whFXL+vg==
X-Received: by 10.99.45.131 with SMTP id t125mr11260502pgt.267.1521658982754; Wed, 21 Mar 2018 12:03:02 -0700 (PDT)
Received: from [192.168.178.30] (86.225.69.111.dynamic.snap.net.nz. [111.69.225.86]) by smtp.gmail.com with ESMTPSA id z9sm4770958pfg.183.2018.03.21.12.03.00 for <v6ops@ietf.org> (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Wed, 21 Mar 2018 12:03:01 -0700 (PDT)
Sender: Brian Carpenter <becarpenter46@gmail.com>
To: v6ops@ietf.org
References: <152162545088.6103.10266745621515516124@ietfa.amsl.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
Message-ID: <38053359-601a-fc03-ea95-4b173cf0bd15@gmail.com>
Date: Thu, 22 Mar 2018 08:03:03 +1300
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.6.0
MIME-Version: 1.0
In-Reply-To: <152162545088.6103.10266745621515516124@ietfa.amsl.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/BalySGkGb2fj8_QfTXRoF93DHh8>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-03.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: Wed, 21 Mar 2018 19:03:06 -0000

Hi,

I think Section 1.3 makes the scope much clearer, thanks.

Maybe a couple of points need to be added to the Abstract too:

 This document is not designed to apply to consumer devices; it is
 up to each provider or equipment purchaser to determine how best to
 apply it to their environment.

Regards
   Brian

On 21/03/2018 22:44, internet-drafts@ietf.org wrote:
> 
> A New Internet-Draft is available from the on-line Internet-Drafts directories.
> This draft is a work item of the IPv6 Operations WG of the IETF.
> 
>         Title           : Requirements for IPv6 Routers
>         Authors         : Zaid Ali Kahn
>                           John Brzozowski
>                           Russ White
> 	Filename        : draft-ietf-v6ops-ipv6rtr-reqs-03.txt
> 	Pages           : 32
> 	Date            : 2018-03-21
> 
> Abstract:
>    The Internet is not one network, but rather a collection of networks.
>    The interconnected nature of these networks, and the nature of the
>    interconnected systems that make up these networks, is often more
>    fragile than it appears.  Perhaps "robust but fragile" is an
>    overstatement, but the actions of each vendor, implementor, and
>    operator in such an interconnected environment can have a major
>    impact on the stability of the overall Internet (as a system).  The
>    widespread adoption of IPv6 could, particularly, disrupt network
>    operations, in a way that impacts the entire system.
> 
>    This time of transition is an opportune time to take stock of lessons
>    learned through the operation of large scale networks on IPv4, and
>    consider how to apply these lessons to IPv6.  This document provides
>    an overview of the design and architectural decisions that attend
>    IPv6 deployment, and a set of IPv6 requirements for routers,
>    switches, and middleboxes deployed in IPv6 networks.  The hope of the
>    editors and contributors is to provide the necessary background to
>    guide equipment manufacturers, protocol implementors, and network
>    operators in effective IPv6 deployment.
> 
> 
> The IETF datatracker status page for this draft is:
> https://datatracker.ietf.org/doc/draft-ietf-v6ops-ipv6rtr-reqs/
> 
> There are also htmlized versions available at:
> https://tools.ietf.org/html/draft-ietf-v6ops-ipv6rtr-reqs-03
> https://datatracker.ietf.org/doc/html/draft-ietf-v6ops-ipv6rtr-reqs-03
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-v6ops-ipv6rtr-reqs-03
> 
> 
> Please note that it may take a couple of minutes from the time of submission
> until the htmlized version and diff are available at tools.ietf.org.
> 
> Internet-Drafts are also available by anonymous FTP at:
> ftp://ftp.ietf.org/internet-drafts/
> 
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>