IETF Logo Mail Archive

Re: [v6ops] Fwd: New Version Notification for draft-hilliard-v6ops-host-addr-update-00.txt

Ted Lemon <mellon@fugue.com> Wed, 19 July 2017 06:24 UTC

Return-Path: <mellon@fugue.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 A8BD412EC0B for <v6ops@ietfa.amsl.com>; Tue, 18 Jul 2017 23:24:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.899
X-Spam-Level:
X-Spam-Status: No, score=-1.899 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, 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=fugue-com.20150623.gappssmtp.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 jWFT6Jfl_nww for <v6ops@ietfa.amsl.com>; Tue, 18 Jul 2017 23:23:59 -0700 (PDT)
Received: from mail-pg0-x229.google.com (mail-pg0-x229.google.com [IPv6:2607:f8b0:400e:c05::229]) (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 CD61A127369 for <v6ops@ietf.org>; Tue, 18 Jul 2017 23:23:59 -0700 (PDT)
Received: by mail-pg0-x229.google.com with SMTP id 123so25498254pgj.1 for <v6ops@ietf.org>; Tue, 18 Jul 2017 23:23:59 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=gFPEvTJtOnl54cRZkjEXyyiCFQeH4a6YksMzpGhhOYY=; b=OkmzdKE+w5VxlSy5hVGHkg6ggropmNftbLy3AKy7ewDmgxI4Wl1jJuqbQhslRRwfnC rAxFOC7PSYQC2vZKQDaMqwvp+mn22JPvTv9WQIOLU5MyajGYmfRRYrUPkYWHclcUJ/vS psxTjf3J/M4f7f7VXxig9rFurD8n/jHv6HidLYek1J5JRAwrPMU43XsD2xjwEwYznWA5 jjIOTButCp3N5+vWjKcpEDrthP7EmyMN48FB9t008qmKE9JeNYRGWWzWR3n9xnA71DhX 4SPjinB85HKWkyOsTljyeAYvC9RuMoHWHsfd7D9XSleoY7xLrjkkOxHkJJXbYZtzTHgr XrXA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=gFPEvTJtOnl54cRZkjEXyyiCFQeH4a6YksMzpGhhOYY=; b=KPeIbYOsZjPAhsgRWpt0iRBlNpbVyM/w7GCYieoucIMLHjHzilMLxNenCinog5b2Ww lt7ZCPNJg79kE1cVxGcMNYk6yMqLoL7ydExjp8ij7iq5WrgidyNYdxS/TBl+Lbg2kXys yNmEIvahGq6WYFWd+ZItVZ7eeFIphV5t891nSkov8Hd1et4h5TgUuW3YvuOAyWMQIAPL piNAGay2ZI1MrBXOP80s6ZS81FczC6nWq+rDKw1V4WUjHb9ebnyGszEmvezfIGWQDnUW 2Zlj2uuNmDHkgwJY5Gi9EQGHGTtIYsiDnQqrTnzl8QoUHGYyOps2LSnH8bYwTyPzb8JT 108g==
X-Gm-Message-State: AIVw11200L0HbZgPAj2sRysztgJp/D7dPFVepAAZdPFu4IKbY9uJilNz LddsacK03EO2M4cMW1PIHY+kkMT5nZ6k
X-Received: by 10.99.62.65 with SMTP id l62mr1443166pga.220.1500445439241; Tue, 18 Jul 2017 23:23:59 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.100.181.42 with HTTP; Tue, 18 Jul 2017 23:23:18 -0700 (PDT)
In-Reply-To: <CAKD1Yr2gMb97SAxG6dZ87xRtGQ4_aUnnjeHAYi-U=5JUvnXVZg@mail.gmail.com>
References: <596CF817.8040900@foobar.org> <CAFU7BAQ5h5dHKmDbOHo9+JCgo+WZpQmctf8F+_0OfJ0dV=tmww@mail.gmail.com> <d3413c76-59ac-5bb0-9122-12881a8d5df7@gmail.com> <CAKD1Yr2gMb97SAxG6dZ87xRtGQ4_aUnnjeHAYi-U=5JUvnXVZg@mail.gmail.com>
From: Ted Lemon <mellon@fugue.com>
Date: Wed, 19 Jul 2017 08:23:18 +0200
Message-ID: <CAPt1N1myybvgEmdzSYmA6SJPwD8rX=X3AuKkMw5qFFZKNMGW1w@mail.gmail.com>
To: Lorenzo Colitti <lorenzo@google.com>
Cc: "Brian E. Carpenter" <brian.e.carpenter@gmail.com>, "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c18ff6a6945560554a5ade6"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/wKeYJHL7XIawQscjsta9G4p6kiI>
Subject: Re: [v6ops] Fwd: New Version Notification for draft-hilliard-v6ops-host-addr-update-00.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, 19 Jul 2017 06:24:02 -0000

But, to be clear, if you do not follow the RECOMMENDation, you are still in
spec, because it is a RECOMMENDation, not a REQUIREment.

On Wed, Jul 19, 2017 at 8:11 AM, Lorenzo Colitti <lorenzo@google.com> wrote:

> On 19 Jul 2017 01:33, "Brian E Carpenter" <brian.e.carpenter@gmail.com>
> wrote:
>
> Nothing in RFC7934 says that any part of DHCPv6 is NOT RECOMMENDED
> (or SHOULD NOT be used, which is the same thing). Specifically,
> there is no normative statement whatever about IA_NA or IA_TA.
>
>
> But it does make a normative recommendation against their exclusive use.
>
> Specifically, it says it is RECOMMENDED to give hosts the ability to form
> new addresses without explicit requests to the network. That recommendation
> cannot be met on a network that *only* provides addresses via IA_NA / IA_TA.
>
> So while it makes no normative recommendation about IA_NA / IA_TA
> themselves, it does make a normative recommendation against running a
> network that uses IA_NA / IA_TA as its only address assignment mechanism.
>
> _______________________________________________
> v6ops mailing list
> v6ops@ietf.org
> https://www.ietf.org/mailman/listinfo/v6ops
>
>

v2.23.0 | Report a Bug | By Email