IETF Logo Mail Archive

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

Lorenzo Colitti <lorenzo@google.com> Mon, 08 May 2017 02:11 UTC

Return-Path: <lorenzo@google.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 D9EC1128DF2 for <v6ops@ietfa.amsl.com>; Sun, 7 May 2017 19:11:11 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.301
X-Spam-Level:
X-Spam-Status: No, score=-1.301 tagged_above=-999 required=5 tests=[BAYES_05=-0.5, 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=-0.001, 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 sX8mhVFAupz1 for <v6ops@ietfa.amsl.com>; Sun, 7 May 2017 19:11:10 -0700 (PDT)
Received: from mail-vk0-x22a.google.com (mail-vk0-x22a.google.com [IPv6:2607:f8b0:400c:c05::22a]) (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 2AB621293EC for <v6ops@ietf.org>; Sun, 7 May 2017 19:11:10 -0700 (PDT)
Received: by mail-vk0-x22a.google.com with SMTP id v20so21356093vke.2 for <v6ops@ietf.org>; Sun, 07 May 2017 19:11:10 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=N7GUUUthjbPJ/+OXEreLDTYvk+LhnnmM4Ykbev3JYiQ=; b=ZT+NlKL9gVUOW++XR2w6JOny+j2AvzwOrg9dzek+0K7cB5IvhucAcutCAdISpOpxhy gZweJ+BP5GQOGEkj+PsMqe/SO0FDixaHL0B/K8m2mgZS22U9iCEhnhXM6G3eFYpIrQVq //aXOKe6lsWLCrO6NTDbBmNwBhptM7B5fVeGMrHSAjcNNRdh9MSLmQCtU95lk6veRFQM BWjANKZI/mmm0gMU5g8o9lmONr5VzHJ37JzFi8FuH5xfJL4yBBjcafG2xMV9JNo6PpPe gP90XZRWTmrlVW5vjgzKGRVTSXWhZH2l9MM+jYRf3nDX0w+atceOgTj2W3QQRvqk/ROn 0PUg==
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; bh=N7GUUUthjbPJ/+OXEreLDTYvk+LhnnmM4Ykbev3JYiQ=; b=Qr7Zb9bGMbqysiUrC8hXxMoOKjUIPyB0w3XWZaMPKznLUfcNDLDQS7I6MuTtAYWhcW MsiYSJjF3mHMV54T1cc7iLmRJmxLepVa7y/SSft33Au1ozWeGp3YFFyoGFnZiw/3Erb6 /RNTpoALK1LTLVZP3rG1lHEZqQNkpYF9byK8xRsf9XMqQBn8xet2215yQmRu1Q5HOxi2 SHksUCPJfp84b9OvZ3F6jwDcKY4enmv4PaFT4hsXJeN+aQIwBAMwSMVpy0OrJst0XEBG HiyNPY25iBcIrEi7Qucs8XQUTf3iX2Dd6JYkwDSnKTHSkzMtibikGqbIRDPR1hxub48j l5EQ==
X-Gm-Message-State: AODbwcAOYo4q7CDMR/34/ZAwiIFqe7rPaMe6vuT2+/pF7Xb8z+xVVsEP F3+xD+UjBLa7a3fbuAbob7pswLtx2Jr+/vrJ5A==
X-Received: by 10.31.12.204 with SMTP id 195mr7383794vkm.18.1494209468747; Sun, 07 May 2017 19:11:08 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.31.148.145 with HTTP; Sun, 7 May 2017 19:10:48 -0700 (PDT)
In-Reply-To: <149402169430.8512.11192508581005769547@ietfa.amsl.com>
References: <149402169430.8512.11192508581005769547@ietfa.amsl.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Mon, 08 May 2017 11:10:48 +0900
Message-ID: <CAKD1Yr2Z=HrLyS5578fZ5s5Qnaf+aT=A_O3D-+9FKXOzsFPxZA@mail.gmail.com>
To: "v6ops@ietf.org WG" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="001a114558b49b432f054ef9c09c"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/ZBuPcbvZy6hdLwT6MgVv_D0tGDw>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-ipv6rtr-reqs-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: Mon, 08 May 2017 02:11:12 -0000

On Sat, May 6, 2017 at 7:01 AM, <internet-drafts@ietf.org> wrote:

>         Title           : Requirements for IPv6 Routers
>         Authors         : Zaid Ali Kahn
>                           John Brzozowski
>                           Russ White
>         Filename        : draft-ietf-v6ops-ipv6rtr-reqs-00.txt
>

As Ted has stated many times, this text:

======
 Routers supporting IPv6, and intended for user facing
   connections, MUST support:

   o  [RFC3646]: DNS Configuration options for Dynamic Host
      Configuration Protocol for IPv6 (DHCPv6).
======

needs clarification. Does it mean that:

   1. A router MUST contain a stateless DHCPv6 server implementation that
   supports the DNS option?
   2. A router MUST contain a DHCPv6 relay implementation that supports the
   DNS option?
   3. If a router contains an DHCPv6 server or relay implementation, then
   that implementation supports the DNS option?

#1 or #2 would be a change to the IPv6 node requirements, which say
<https://tools.ietf.org/html/rfc6434#section-12.3>:

====
   support for DHCP
   server functionality on routers is optional.  However, routers
   targeted for deployment within more complex scenarios (as described
   above) SHOULD support relay agent functionality
====

I don't think it makes sense to say #1 or #2 and thus say that all IPv6
routers MUST support DHCPv6, because:

   1. Other than for home gateways where DHCPv6 is required, I'd expect
   that the vast majority of routers don't actually support it at all (at
   least not in all feature sets).
   2. In most places in the network there's not even any point in
   supporting it, because it will never be used. DHCPv6 can only ever be used
   in routers that serve as first-hop routers for hosts, so a backbone router
   will never need a DHCPv6 server or relay.

#3 does make sense.

v2.23.0 | Report a Bug | By Email