IETF Logo Mail Archive

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

Brian E Carpenter <brian.e.carpenter@gmail.com> Tue, 14 November 2023 19:36 UTC

Return-Path: <brian.e.carpenter@gmail.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 61F98C15C29A for <v6ops@ietfa.amsl.com>; Tue, 14 Nov 2023 11:36:13 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.199
X-Spam-Level:
X-Spam-Status: No, score=-2.199 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, FREEMAIL_FROM=0.001, NICE_REPLY_A=-0.091, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.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 jeS5l-hmlonS for <v6ops@ietfa.amsl.com>; Tue, 14 Nov 2023 11:36:11 -0800 (PST)
Received: from mail-pl1-x635.google.com (mail-pl1-x635.google.com [IPv6:2607:f8b0:4864:20::635]) (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 48CD4C1522C6 for <v6ops@ietf.org>; Tue, 14 Nov 2023 11:36:11 -0800 (PST)
Received: by mail-pl1-x635.google.com with SMTP id d9443c01a7336-1cc34c3420bso46970585ad.3 for <v6ops@ietf.org>; Tue, 14 Nov 2023 11:36:11 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20230601; t=1699990571; x=1700595371; darn=ietf.org; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=lCdKAwU4Ysb9awD7N9KU7DWRmh4tZdO8C3tbPlqhKcU=; b=bqqM38/k8MOitNd25dRc1JC4nbBh58dMmhMybZuKMchg58oO5VL3vChfMbWheTYzx1 jHz68WvyS0qotoWDxeMbYMrg57ExJM2IrXqJzcoUhuVg1UZtO0CFWjMO5Xawn4vtUvhb pJSBApaP4B9iB/sDAP7u3clcPY4zfHAElQJdyEpcQNAJBoNKpvsYto8j6EEfR0o49QbR QJdB8oyri/tU2jMHe0nv2nSprp5yuuuUmrlX366AXcg7kvlxc5MPZ0pC0WSP7LOpwkHM SQwS113OPyXPKuY9vzubxovV160kT5U5387OfhiC2fA2hJmMGM2KUXKyRZ3GMCL+WoiX lFlA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1699990571; x=1700595371; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=lCdKAwU4Ysb9awD7N9KU7DWRmh4tZdO8C3tbPlqhKcU=; b=LBqnl5qgD3T5GX6LI05U+RvmF8/J2oJcByT4nrrhohfTIMzS4f9Db+6lrXsi3vADhc 75LipZp21keAqZn5AvusYyzLZcYrs5iAaaEXoHON6lobFiSbXbSfbtxVgetpW0/voHkD tfeRjPeGjLkXqwiYUcArIGFUZR1baVzX9azIxiifU2xWyvOviBMtr8yOrItFCSreTlq/ rJkek965onHli/+4gkSLJd6x6ealcbjtB94gC2pO56Gg4Sl8ps7FZbiegcFpqpzJPJ+0 B5j4CqKabnLB43DqzznF2qLCkz0d32E3Nmjh+lc+4BIB6W32oqXvf+wE9CWKWHlNZ9a1 wnqQ==
X-Gm-Message-State: AOJu0Yxat7Idaz3llIrfMnYE/wtX/iraCNLtPT/+QBoPeVIRBtydAq+L vRRj+GiK5Rqo1D4H+m8N4Uc=
X-Google-Smtp-Source: AGHT+IEjAJceLjndPAZ0RCmz2Nz0uOag9IqWoR+S9soPOSrITT1MqCQWEkzht98tOMqn4j4hf+hVlA==
X-Received: by 2002:a17:902:ce12:b0:1bc:6861:d746 with SMTP id k18-20020a170902ce1200b001bc6861d746mr4739593plg.58.1699990570693; Tue, 14 Nov 2023 11:36:10 -0800 (PST)
Received: from ?IPV6:2406:e003:110d:5301:8cb6:a2c:7461:4047? ([2406:e003:110d:5301:8cb6:a2c:7461:4047]) by smtp.gmail.com with ESMTPSA id h10-20020a170902f7ca00b001b8a00d4f7asm6065487plw.9.2023.11.14.11.36.08 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Tue, 14 Nov 2023 11:36:10 -0800 (PST)
Message-ID: <387c303f-ac8a-57a5-7123-734257f9955b@gmail.com>
Date: Wed, 15 Nov 2023 08:36:05 +1300
MIME-Version: 1.0
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:91.0) Gecko/20100101 Thunderbird/91.10.0
Content-Language: en-US
To: Timothy Winters <tim@qacafe.com>, Ole Troan <otroan@employees.org>
Cc: v6ops list <v6ops@ietf.org>
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> <CAJgLMKs=rCG019Sjaf2tuJhEX6s7Uo_hYjPv_izFNo83zhYrTw@mail.gmail.com> <3A52D975-0CC2-425B-914A-8A76572D5811@employees.org> <CAJgLMKtGRvXaf+4xPSe9aO3SDtQLmwsopCsxTj+JBOz38sujJQ@mail.gmail.com>
From: Brian E Carpenter <brian.e.carpenter@gmail.com>
In-Reply-To: <CAJgLMKtGRvXaf+4xPSe9aO3SDtQLmwsopCsxTj+JBOz38sujJQ@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"; format="flowed"
Content-Transfer-Encoding: base64
Archived-At: <https://mailarchive.ietf.org/arch/msg/v6ops/Q1w2vi43u1RknVKKiOnWEjOjpfc>
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 19:36:13 -0000

On 15-Nov-23 02:38, Timothy Winters wrote:
> Hi Ole,
> 
> I think that's a path forward that can work for me.

+1
   Brian

> 
> ~Tim
> 
> On Tue, Nov 14, 2023 at 8:28 AM Ole Troan <otroan@employees.org <mailto:otroan@employees.org>> wrote:
> 
>     Tim,
> 
>      > 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?
> 
>     My take is that if we knew exactly how it would work and there was running code, we should put it into 7084bis.
>     If we don’t know how to do it, then we should use a separate document.
> 
>     I’m a little unsure, given the two documents I forwarded to the link earlier.
>     An interior router would have to dynamically detect upstream / downstream…
> 
>     Perhaps the best is to work out all the issues in your document, then merge requirements that are ready into 7084bis?
> 
>     Cheers,
>     Ole
>

v2.23.0 | Report a Bug | By Email