IETF Logo Mail Archive

Re: [v6ops] Requirements for IPv6 routers in various locations

Joe Touch <touch@isi.edu> Wed, 22 February 2017 01:18 UTC

Return-Path: <touch@isi.edu>
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 6B11C1294C8 for <v6ops@ietfa.amsl.com>; Tue, 21 Feb 2017 17:18:03 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.901
X-Spam-Level:
X-Spam-Status: No, score=-6.901 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-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 trNAuOjEPRIF for <v6ops@ietfa.amsl.com>; Tue, 21 Feb 2017 17:18:02 -0800 (PST)
Received: from boreas.isi.edu (boreas.isi.edu [128.9.160.161]) (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 793751294BF for <v6ops@ietf.org>; Tue, 21 Feb 2017 17:18:02 -0800 (PST)
Received: from [128.9.184.189] ([128.9.184.189]) (authenticated bits=0) by boreas.isi.edu (8.13.8/8.13.8) with ESMTP id v1M1HSQw024676 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Tue, 21 Feb 2017 17:17:29 -0800 (PST)
To: Fred Baker <fredbaker.ietf@gmail.com>, IPv6 Ops WG <v6ops@ietf.org>
References: <148763027040.25952.5914924936449771028.idtracker@ietfa.amsl.com> <692043A0-04F2-46EA-84D2-D4964E925C6B@consulintel.es> <03B10A5B-ABE3-4515-90B9-D16A41039229@google.com> <2D09D61DDFA73D4C884805CC7865E6114DAC7803@GAALPA1MSGUSRBF.ITServices.sbc.com> <EC9120C1-E135-4BD9-9B8B-AD9443261C13@gmail.com>
From: Joe Touch <touch@isi.edu>
Message-ID: <a52faa18-6ee5-b683-d1a1-36fdb956e10d@isi.edu>
Date: Tue, 21 Feb 2017 17:17:26 -0800
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.7.1
MIME-Version: 1.0
In-Reply-To: <EC9120C1-E135-4BD9-9B8B-AD9443261C13@gmail.com>
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
X-ISI-4-43-8-MailScanner: Found to be clean
X-MailScanner-From: touch@isi.edu
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZQwoL5ifz6F1cnHhrJMVmhHM_rw>
Subject: Re: [v6ops] Requirements for IPv6 routers in various locations
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.17
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, 22 Feb 2017 01:18:03 -0000


On 2/21/2017 5:09 PM, Fred Baker wrote:
> This argument is essentially what I was referring to with respect to draft-ali-ipv6rtr-reqs when I said we had multiple markets that RFC 1812 didn't have to address. They include, at least, ISP, content network, data center, enterprise, residential, IoT, and mobile wireless networks. Those markets have differing non-exclusive sets of requirements.
Is there a way to focus on the core requirements that all routers need
to support in this doc, assuming that there are lots of things a router
in general MAY also do...

And then leave it to other documents to focus on the additional
requirements (or relaxations of SHOULDs) that apply to these environments?

Joe

v2.23.0 | Report a Bug | By Email