Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt
Lorenzo Colitti <lorenzo@google.com> Fri, 19 May 2023 01:50 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 71606C15106C for <v6ops@ietfa.amsl.com>; Thu, 18 May 2023 18:50:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.595
X-Spam-Level:
X-Spam-Status: No, score=-17.595 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_BLOCKED=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] 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 ([50.223.129.194]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 2KBM5TO4u6Xb for <v6ops@ietfa.amsl.com>; Thu, 18 May 2023 18:49:58 -0700 (PDT)
Received: from mail-vk1-xa29.google.com (mail-vk1-xa29.google.com [IPv6:2607:f8b0:4864:20::a29]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 3B0E2C151064 for <v6ops@ietf.org>; Thu, 18 May 2023 18:49:58 -0700 (PDT)
Received: by mail-vk1-xa29.google.com with SMTP id 71dfb90a1353d-456d6ef4449so528291e0c.3 for <v6ops@ietf.org>; Thu, 18 May 2023 18:49:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20221208; t=1684460997; x=1687052997; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=pFi6jH39TFL7lWk/XCZVPr1A+yNvuYf5VKpjFl7EKTA=; b=lAZ+P36oXJB6DLNgzG1B/xfKBiVn9bFW5Saf54Z5yeuKTUqsvLi5CTHQPhf9fFJp27 SdPDHrPkqCwtJkhg5Cd7J3i/s//F+5ayhFb+QjXA+DRb/KfsMBsk4WlIGoyiVEXGMx86 GAJ3BF2Q/XjUgrzdT1QR8FlzDLTib6Cz9HUVjS3nX+O+5uA5qZTtSWOXFeN8kuGTKI8L 46SzUlKpTPH94WJIokeIaeNceHCafXNGZxDwZTChzUxlh/Ww0frSb2NGbRMIOmmJtqmI sH9crc+G027TCGo0JxNbZCrrPaUd+jgcNEyIMoeT3G7WBUBVwt61REqeND4OVvkR/Cj/ MJ3A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1684460997; x=1687052997; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=pFi6jH39TFL7lWk/XCZVPr1A+yNvuYf5VKpjFl7EKTA=; b=Mp7/0x0BPLYULROuFTbLCVAq0XIprgHR2M43VOqKHqVwlSoyC5ABmwLo7Tprdv38Rp eK42eFYiVGGku1s1YJojmoWvmmhj9JmGVOEbliaK/TpXnx2p52QNBKybeHOzyRIzcl4n eao4bYPrBnaRovnzztK2AFQDA5uL4YrxA32jpXmaP+VbVLCENiX0/9bPTHvDcnA1KnP3 uLnVBgIwC8p3d9XQohptdTNamvfnpPK9ooVKApwsWt8mYlCUt717kdBoRvJwYfWXvyPL 0kPQ7YVGTJZ2XSnymSvi+wkcOnsaAP3RV5nxWxHpoA9azUs9mzam4j4MVJteO9BSx+I0 zhqg==
X-Gm-Message-State: AC+VfDzs2MVyT9pZtgM+fKVMWXYSoTLk0rlD8Li18HyIUmYivSxWI19R l4532v4O4rLnBl5Gnjh1F2cDgV/ly03aIckCGgJWpED48XBu+UitRlOkLA==
X-Google-Smtp-Source: ACHHUZ5Pm8mMbfQwTgX3aAqSKJOsDINEFHY5iWREXnuKc5x9n2ANfg9ypeOmIy36cDGBqqrtCEirmzJ+542up3GnPDs=
X-Received: by 2002:a1f:c183:0:b0:44f:d1d6:1978 with SMTP id r125-20020a1fc183000000b0044fd1d61978mr89847vkf.5.1684460996667; Thu, 18 May 2023 18:49:56 -0700 (PDT)
MIME-Version: 1.0
References: <168442407010.2544.7512872622955254077@ietfa.amsl.com> <ed88eaba055b4dbfa079a6dd0752c910@huawei.com> <8936207b-860e-975e-4052-6c1598208d92@gmail.com>
In-Reply-To: <8936207b-860e-975e-4052-6c1598208d92@gmail.com>
From: Lorenzo Colitti <lorenzo@google.com>
Date: Fri, 19 May 2023 10:49:44 +0900
Message-ID: <CAKD1Yr01PUxnw2MhtTp=TLyaMbMUuE56UkjuYhZAw9_rKQmmww@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Vasilenko Eduard <vasilenko.eduard=40huawei.com@dmarc.ietf.org>, "v6ops@ietf.org" <v6ops@ietf.org>
Content-Type: multipart/alternative; boundary="00000000000058869605fc0223bf"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/nv41jnY-vvjnTUH6CYQGZ93qKEo>
Subject: Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt
X-BeenThere: v6ops@ietf.org
X-Mailman-Version: 2.1.39
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: Fri, 19 May 2023 01:50:00 -0000
Ah, good catch, yes. We'll change it to hosts. On Fri, May 19, 2023 at 6:02 AM Brian E Carpenter < brian.e.carpenter@gmail.com> wrote: > On 19-May-23 03:59, Vasilenko Eduard wrote: > > Section 4 is still misleading people that SLAAC (and /64 as a > consequence) are mandatory. > > The draft says: > > because all IPv6 nodes are required to support SLAAC. > > This is not quite true. BCP 220 (RFC 8504) says: > > Hosts MUST support IPv6 Stateless Address Autoconfiguration. > > In the context of this draft, that discrepancy is unimportant. > > Of course, sites MAY choose to deploy DHCPv6 instead of SLAAC, but that > doesn't remove the MUST for hosts. > > Brian > > > In fact, section 4 assumes some special "complex host" that has a > virtual router inside. Is it still a host? Does the virtual router need > additional specifications? > > Albeit, in the majority of cases, a normal host would not have a virtual > router inside. > > Moreover, even virtualized host (with many VMs or Containers) would have > a virtual switch inside, not a router. > > Hence, for the great majority of cases, SLAAC is not relevant. > > Section 4 is still misleading. > > > > Nothing in the draft is about the possibility to use prefixes different > from /64. > > > > The draft is still targeted for one corner case (with a virtual router > inside the host), > > Discarding the possibility to use the solution on a much broader set of > use cases. > > > > Ed/ > > -----Original Message----- > > From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of > internet-drafts@ietf.org > > Sent: Thursday, May 18, 2023 6:35 PM > > To: i-d-announce@ietf.org > > Cc: v6ops@ietf.org > > Subject: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-device-00.txt > > > > > > A New Internet-Draft is available from the on-line Internet-Drafts > directories. This Internet-Draft is a work item of the IPv6 Operations > (V6OPS) WG of the IETF. > > > > Title : Using DHCP-PD to Allocate Unique IPv6 Prefix per > Device in Broadcast Networks > > Authors : Lorenzo Colitti > > Jen Linkova > > Xiao Ma > > Filename : draft-ietf-v6ops-dhcp-pd-per-device-00.txt > > Pages : 14 > > Date : 2023-05-18 > > > > Abstract: > > This document discusses the IPv6 deployment scenario when individual > > devices connected to broadcast networks (like WiFi hotspots or > > enterprise networks) are allocated unique prefixes via DHCP-PD. > > > > The IETF datatracker status page for this Internet-Draft is: > > https://datatracker.ietf.org/doc/draft-ietf-v6ops-dhcp-pd-per-device/ > > > > There is also an HTML version available at: > > > https://www.ietf.org/archive/id/draft-ietf-v6ops-dhcp-pd-per-device-00.html > > > > Internet-Drafts are also available by rsync at rsync.ietf.org: > :internet-drafts > > > > > > _______________________________________________ > > v6ops mailing list > > v6ops@ietf.org > > https://www.ietf.org/mailman/listinfo/v6ops > > > > _______________________________________________ > > v6ops mailing list > > v6ops@ietf.org > > https://www.ietf.org/mailman/listinfo/v6ops > > _______________________________________________ > v6ops mailing list > v6ops@ietf.org > https://www.ietf.org/mailman/listinfo/v6ops >
- [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-per-… internet-drafts
- Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-… Brian E Carpenter
- Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-… Vasilenko Eduard
- Re: [v6ops] I-D Action: draft-ietf-v6ops-dhcp-pd-… Lorenzo Colitti