Re: [v6ops] WG Adoption call for draft-winters-v6ops-cpe-lan-pd-04

Timothy Winters <tim@qacafe.com> Tue, 14 November 2023 13:19 UTC

Return-Path: <tim@qacafe.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 E15E6C15107E for <v6ops@ietfa.amsl.com>; Tue, 14 Nov 2023 05:19:00 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -7.106
X-Spam-Level:
X-Spam-Status: No, score=-7.106 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_DBL_BLOCKED_OPENDNS=0.001, URIBL_ZEN_BLOCKED_OPENDNS=0.001] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=qacafe.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 uNID-MZKrcGG for <v6ops@ietfa.amsl.com>; Tue, 14 Nov 2023 05:18:56 -0800 (PST)
Received: from mail-pg1-x52a.google.com (mail-pg1-x52a.google.com [IPv6:2607:f8b0:4864:20::52a]) (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 9FB23C14CE27 for <v6ops@ietf.org>; Tue, 14 Nov 2023 05:18:56 -0800 (PST)
Received: by mail-pg1-x52a.google.com with SMTP id 41be03b00d2f7-5bd85b1939aso3471047a12.2 for <v6ops@ietf.org>; Tue, 14 Nov 2023 05:18:56 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=qacafe.com; s=google; t=1699967935; x=1700572735; darn=ietf.org; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc:subject:date:message-id:reply-to; bh=6Zc4HfsYnw66w4fELq4ybss2aFYbgSPKViysz+Lin+I=; b=mAF3r8SDWonA5DXeCNVewoMr1UkQdLQ/zGndwb72xrkdNo+5soCceOH1x3MjiMLdgs BQxjwaXoP/7bC6FcXAvQ3mJdjX0z8P3+1gGl7h1kFuVqAHGBdJdivD/8x/U4sCzgxg/C ihXCYEqqIl3AO2jBszlCexnRoeLcCOgzbBZrA=
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699967935; x=1700572735; 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=6Zc4HfsYnw66w4fELq4ybss2aFYbgSPKViysz+Lin+I=; b=jGnyVliZ/XmvNHPmGBoo6BTcT9MvGYpjTToazQYlgxdVAOoNQvLpGIj4ezEukjOjH7 bdTL8r8bMf6z/r91sBkJPXjD3CQ9wDVjrnXpaeP5s1mRTbRvKXl/T9Rj2SIpKCwckfzX /ECynrUOrDpOh/IF9hRTE8IEX4ikJFRpGX/Mf4N2zIfJKPkWTBrCqsCpSaIuchM9ddbE XHwjIIvz2UJE522VndGFJXwk30oU1Z1VJaaGlBKTjNfnkUsle4lSS7bpdYkDvoNO57I1 PLYLkPqTZlCrxnEB7P+RTUFHA+Qe47Lt3hIpUxJuoj2jy1aOQlomI46x3ayy4c7AGg8x ECsg==
X-Gm-Message-State: AOJu0YwKZaJhUllsb63hY+2jgkFkIugGmCDn+GTxKK+X02uzBXnzSBVA LH4hoMeY7cOou9fqp6aiiOEJaAoqLoCPPj0H9JiWVQ==
X-Google-Smtp-Source: AGHT+IHpAd3bWxD9V4w98+ZQ+jGNKQW1O6RXMjDLqjQfcWyzGTws+QzqekCQxMFY86JjQ8N9nYEEmqSMgK25DpcpyEA=
X-Received: by 2002:a17:90b:4f88:b0:27c:f016:49a2 with SMTP id qe8-20020a17090b4f8800b0027cf01649a2mr6993509pjb.7.1699967935169; Tue, 14 Nov 2023 05:18:55 -0800 (PST)
MIME-Version: 1.0
References: <b35c7737f1b54a848f23b2fc9d54993f@huawei.com> <CAPt1N1=DYLN1vRox8Ld+96Bf6=iy-hEat5RbVC6xuPo2QMrieQ@mail.gmail.com> <6eb00cab-30d4-45fa-9cd7-a604b982eba2@hit.bme.hu> <CAPt1N1=4+Q2VmD=k2PS3y+qk2ZRGeqW45Y+yOm5W+v9G4MQqug@mail.gmail.com> <CAJgLMKv24axzRFGmLmfrS9gqzr4xE1kTu2YWo5oO=H=KO5BPRQ@mail.gmail.com> <CAPt1N1n4iDuRmSOub475BgcaQfMf_Je-mhaGbaU_VxSR_uMgig@mail.gmail.com> <6222a2d7-685f-872a-2d1d-5c07b2962350@gmail.com>
In-Reply-To: <6222a2d7-685f-872a-2d1d-5c07b2962350@gmail.com>
From: Timothy Winters <tim@qacafe.com>
Date: Tue, 14 Nov 2023 08:18:43 -0500
Message-ID: <CAJgLMKs=rCG019Sjaf2tuJhEX6s7Uo_hYjPv_izFNo83zhYrTw@mail.gmail.com>
To: Brian E Carpenter <brian.e.carpenter@gmail.com>
Cc: Ted Lemon <mellon@fugue.com>, v6ops@ietf.org
Content-Type: multipart/alternative; boundary="000000000000e7e104060a1ca088"
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/YkV2RBEnfZECz534hJQyjxiHx5Q>
Subject: Re: [v6ops] WG Adoption call for draft-winters-v6ops-cpe-lan-pd-04
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: Tue, 14 Nov 2023 13:19:01 -0000

Hi Ted and Brian,

Thanks, at the time I was thinking this was an update to 7084 Routers for
supporting prefix delegation on the LAN.  Do we want to continue this
document as an RFC, dropping the update or just roll it into 7084?

Regards,
Tim

On Mon, Nov 13, 2023 at 9:14 PM Brian E Carpenter <
brian.e.carpenter@gmail.com> wrote:

> On 14-Nov-23 09:52, Ted Lemon wrote:
> > I wonder if this was a miscommunication. "An update" to me means you
> take the document and update it,
>
> In RFC Editor terminology, that is "Obsoletes:"
>
> > not that you write a document that specifies updates to the original
> document.
>
> That is "Updates:" but it's ambiguous (see
> draft-kuehlewind-rswg-updates-tag for the suggested fix).
>
> > It's generally (IMHO) not a good idea to do this unless the update is
> very minor and the document does something else useful, or /at least/ that
> the update is very minor. That's not the case here.
>
> That's probably a point that draft-kuehlewind-rswg-updates-tag should
> cover.
>
>     Brian
>
> >
> > On Mon, Nov 13, 2023 at 1:10 PM Timothy Winters <tim@qacafe.com <mailto:
> tim@qacafe.com>> wrote:
> >
> >     Hi Ted,
> >
> >     This is a question that I was thinking about last week.  When I
> first proposed adding LAN prefix delegation (IETF-115), I asked the v6ops
> working group if we should have a 7084bis or make this a second document
> updating 7084.  The feedback on the list and in the room was to have it be
> an update.
> >
> >     Obviously the working group feels a little bit differently about
> this now with an ongoing 7084bis work starting.   I see two options:
> >
> >      1. Putting out a short document on LAN prefix delegation while we
> work on 7084bis.   7084bis will use whatever comes out of that discussion.
> >      2. Wait for 7084bis and roll this into that.
> >
> >     Gabor, future host might be able prefixes per
> draft-ietf-v6ops-dhcp-pd-per-device.
> >
> >     ~Tim
> >
> >
> >     On Mon, Nov 13, 2023 at 12:33 PM Ted Lemon <mellon@fugue.com
> <mailto:mellon@fugue.com>> wrote:
> >
> >         I guess the question then is why two documents?
> >
> >         On Mon, Nov 13, 2023 at 12:25 PM Gábor LENCSE <lencse@hit.bme.hu
> <mailto:lencse@hit.bme.hu>> wrote:
> >
> >             Hi Ted,
> >
> >             11/13/2023 2:30 PM keltezéssel, Ted Lemon írta:
> >              > I would like to see this work adopted. However, the
> current document
> >              > appears to be a difference update to RFC7084, which I
> think is going
> >              > to be really confusing for anyone reading it, so I think
> this should
> >              > just be a 7084bis, not a separate document that "updates"
> 7084.
> >
> >             There is another document to replace RFC 7084. It is:
> >
> https://datatracker.ietf.org/doc/html/draft-winters-v6ops-rfc7084bis <
> https://datatracker.ietf.org/doc/html/draft-winters-v6ops-rfc7084bis>
> >
> >             Thus, IMHO, draft-winters-v6ops-cpe-lan-pd-04 indeed only
> updates RFC 7084.
> >
> >             Gábor
> >
> >
> >             _______________________________________________
> >             v6ops mailing list
> >             v6ops@ietf.org <mailto:v6ops@ietf.org>
> >             https://www.ietf.org/mailman/listinfo/v6ops <
> https://www.ietf.org/mailman/listinfo/v6ops>
> >
> >         _______________________________________________
> >         v6ops mailing list
> >         v6ops@ietf.org <mailto:v6ops@ietf.org>
> >         https://www.ietf.org/mailman/listinfo/v6ops <
> https://www.ietf.org/mailman/listinfo/v6ops>
> >
> >
> > _______________________________________________
> > v6ops mailing list
> > v6ops@ietf.org
> > https://www.ietf.org/mailman/listinfo/v6ops
>