IETF Logo Mail Archive

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

Fred Baker <fredbaker.ietf@gmail.com> Wed, 22 February 2017 01:29 UTC

Return-Path: <fredbaker.ietf@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 861F11294C9 for <v6ops@ietfa.amsl.com>; Tue, 21 Feb 2017 17:29:19 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2
X-Spam-Level:
X-Spam-Status: No, score=-2 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] 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 IxXFxiAYIrJk for <v6ops@ietfa.amsl.com>; Tue, 21 Feb 2017 17:29:06 -0800 (PST)
Received: from mail-pg0-x231.google.com (mail-pg0-x231.google.com [IPv6:2607:f8b0:400e:c05::231]) (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 09D561294C1 for <v6ops@ietf.org>; Tue, 21 Feb 2017 17:29:06 -0800 (PST)
Received: by mail-pg0-x231.google.com with SMTP id 1so25961341pgi.1 for <v6ops@ietf.org>; Tue, 21 Feb 2017 17:29:06 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CNPztm7YLUkuXVu3zj1TF2TnttEDYYhJyNCqBeMU/Pk=; b=kiOO71EeTncqmYb38aETS6XjevWW2lGRjejI5tNpyi3lWaNg9K8G71eukH4wynp3DF H/n/pDI4uYctFD+ilIkYHYiO6bJE4GmfjEwvCgdPdimWU9iKTtKY/JWVWAUSqZoo08IL Tb2kMHRiRUn1TU9y9ixQAdSFIMfq/23z79J4I0RYdvhNNxXUeR4ST6jwCwRCbNpBxBtB 2aLHj0tgQKIGuBHGhN+9mEdC+hAOgk+tKgYt3v9isY6ImYJ7GLRA8VsxETnbCk3OouQM kBYY5CxmSYocykfM3A0/a9OiD9aZFzTXaDKtFmIXPHB55Plicza22CH5hScKuxoSVj4G K9jA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=CNPztm7YLUkuXVu3zj1TF2TnttEDYYhJyNCqBeMU/Pk=; b=aKHCQyamjTUfv0TEjDOTG/ysdIGfUQyY1meSTgN2Rpy6HyLnRq9xnfKCE22masH0Wx Tq+zUALRdrVJrzwrWGrnJbBtFMVEQirdKK7mtwwkzqW4o1ZeGKyNErn2MQTqpbWOgzS8 MfZ6EdGp01KRslYVsVpZH28RwRQbp4rMdGg5rK79vOb0fFUFet5y94jy3WkZY+wdGARX FhpWEww1+3HlSPAwbGDX3MW8yojkh7+vpYGbjVhDUbKqdXTDyP81AgN0ASgUINBPX8e6 l4DmeTb7oLm/+C6VWFoVmP56KZ62C9YmwDLs9dkBdo3366sU7sjXQdF81JxntIij9IYk Hl+w==
X-Gm-Message-State: AMke39mrVVIOo+LvUTZmgRG21CDj4EQzZOWehgG1Hd/y+Q6M7SMFNF3Ta3O3iX/ASyLkUg==
X-Received: by 10.84.238.1 with SMTP id u1mr44490135plk.174.1487726945621; Tue, 21 Feb 2017 17:29:05 -0800 (PST)
Received: from [192.168.1.15] (wsip-184-191-158-59.sd.sd.cox.net. [184.191.158.59]) by smtp.gmail.com with ESMTPSA id o66sm43077009pfa.119.2017.02.21.17.29.04 (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 21 Feb 2017 17:29:04 -0800 (PST)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
From: Fred Baker <fredbaker.ietf@gmail.com>
In-Reply-To: <a52faa18-6ee5-b683-d1a1-36fdb956e10d@isi.edu>
Date: Tue, 21 Feb 2017 17:29:04 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C5483E13-2155-434D-A2CD-F165577872C0@gmail.com>
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> <a52faa18-6ee5-b683-d1a1-36fdb956e10d@isi.edu>
To: Joe Touch <touch@isi.edu>
X-Mailer: Apple Mail (2.3259)
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/0pXVx_NN1CKoL-VfHQ84WCwdZE0>
Cc: IPv6 Ops WG <v6ops@ietf.org>
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:29:19 -0000

> On Feb 21, 2017, at 5:17 PM, Joe Touch <touch@isi.edu> wrote:
> 
> 
> 
> 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?

There may be; it would be the "core document" I referred to. A document that is accurately described as "7084-bis" would not be that document; 7084 describes a router in a particular application, and probably a particular price point, something called "customer-edge".

v2.23.0 | Report a Bug | By Email