Re: Next steps: IPv6 core specifications to Internet Standard.

Lorenzo Colitti <lorenzo@google.com> Wed, 25 May 2016 04:22 UTC

Return-Path: <lorenzo@google.com>
X-Original-To: ipv6@ietfa.amsl.com
Delivered-To: ipv6@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 168DE12D5FE for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 21:22:23 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -4.126
X-Spam-Level:
X-Spam-Status: No, score=-4.126 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7, RP_MATCHES_RCVD=-1.426, SPF_PASS=-0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.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 qRhDQN0gRLPz for <ipv6@ietfa.amsl.com>; Tue, 24 May 2016 21:22:21 -0700 (PDT)
Received: from mail-yw0-x22f.google.com (mail-yw0-x22f.google.com [IPv6:2607:f8b0:4002:c05::22f]) (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 6261612D5D8 for <ipv6@ietf.org>; Tue, 24 May 2016 21:22:21 -0700 (PDT)
Received: by mail-yw0-x22f.google.com with SMTP id h19so36656578ywc.0 for <ipv6@ietf.org>; Tue, 24 May 2016 21:22:21 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=0EBVE7ojv9Xo2ZDHlKEoNZVbHAu0AgV+oOXkGuNTkjk=; b=Q6qKnlDGjNoDpwwOE7LOHbzEP6gak5vGNId22X99i+OHSxMl5gpvVm9s9rXdpMKJjU Oe9xCx8IyAb1P/xGaoQi7ogyf25MxJboAEEsSHwlIamOXqxNApghCdZHZ3cHMSaCJN5J q97PZewX2mBrgT/Sphy/T/XhqVy3CdaSRVhALx3cLmDUxr4kkIlsb3GkNCvltNYMRKTg 0OYJAy6dbOc43KiBhsCY5KeeXiWcrOLZt3x5I3mWPN16nrqAQE1m71vzhjd/4Lqnk+pb nn5Cw8OzA491ept9PXRdx2N6+GN/mInpzagRl6twNn0Ry4O0oIsJlQ2GWw4Sr4ZhaonY O59Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=0EBVE7ojv9Xo2ZDHlKEoNZVbHAu0AgV+oOXkGuNTkjk=; b=bKcbhUhVC7X5dnuCBQTNvbh8G4SAaUxPj4gJMGNPcKJJ+HkxABtR/WA90tumSoVm48 ETb7raHowzHxsxCRyPDG1y6xltDhyCuc+xTZGAgdMdD28lc9o+ZQeiMNWmTeI9lk80cd R6zO5uUMoRoHnLZJIjrveHgUBC6RPIlyDXRfl2qz26ZzV82GJbDgV36Yb4903SNC23iC mmnhYwTxHOEypCqhiwBlCEwLyRu9qKh85Pdvq8DSssSq1sTbegqjbhnqADUlNSBEVp5A 40NAXKrQF1eZyw3PvcafKBsbW5Qc94RIyhqnVccAIdiDdzCrYcFKGICeOYdEp+BWAUc5 dn0g==
X-Gm-Message-State: ALyK8tLIZ8clarTn6KwKLTH3u9nGGNpcZV/xgQxGFkdjN/xRyMh7YJbrfqslw+/JJGTBHvVqHOqdEcOp6h/KqFLC
X-Received: by 10.37.194.197 with SMTP id s188mr1060560ybf.186.1464150140369; Tue, 24 May 2016 21:22:20 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.37.198.68 with HTTP; Tue, 24 May 2016 21:21:59 -0700 (PDT)
In-Reply-To: <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
References: <025B4B8D-E3B0-450D-9519-6D5D14B8ABC1@employees.org> <57432795.4070602@si6networks.com> <01D432A7-42E5-48CE-BB93-555DDE21CC81@employees.org> <82b95174-1f20-3621-d044-889822dbc0e6@gmail.com> <DB037277-B7BD-4291-8466-5E42BF4B5578@employees.org>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Wed, 25 May 2016 13:21:59 +0900
Message-ID: <CAKD1Yr0ciXOeKjXx0vw+vtxhsUr-BwecL7uV=MKupSH4X4CskA@mail.gmail.com>
Subject: Re: Next steps: IPv6 core specifications to Internet Standard.
To: Ole Troan <otroan@employees.org>
Content-Type: multipart/alternative; boundary="94eb2c054ace047d0d0533a305a9"
Archived-At: <http://mailarchive.ietf.org/arch/msg/ipv6/PYaCdlx_tzxhNkeD3-vbJ-2qMkY>
Cc: 6man WG <ipv6@ietf.org>
X-BeenThere: ipv6@ietf.org
X-Mailman-Version: 2.1.17
Precedence: list
List-Id: "IPv6 Maintenance Working Group \(6man\)" <ipv6.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/ipv6>, <mailto:ipv6-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/ipv6/>
List-Post: <mailto:ipv6@ietf.org>
List-Help: <mailto:ipv6-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ipv6>, <mailto:ipv6-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 25 May 2016 04:22:23 -0000

On Tue, May 24, 2016 at 3:59 PM, <otroan@employees.org> wrote:

> I don't think 4941 _requires_ public addresses. it specifies the behaviour
> _if_ you have them.
>

RFC 4941 does require public addresses:

   1. The text explicitly says in several places that privacy addresses are
   "in addition to" public addresses.
   2. If you don't have a public address, critical parts of the
   specification, such as how to extend the lifetime of privacy addresses when
   receiving an RA, are undefined. An example is the text that says, in
   effect, "when an RA would extend the lifetime of a public address, then
   also extend the lifetime of temporary addresses".

If we want to reclassify it as is, we'll have to accept that the resulting
Internet standard document will only a) define the behaviour for privacy
addresses with a public address, b) say that privacy addresses should be
depreferred by default.