Re: [dhcwg] L2RA

Bernie Volz <bevolz@gmail.com> Wed, 30 August 2023 16:36 UTC

Return-Path: <bevolz@gmail.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 79BF4C151066 for <dhcwg@ietfa.amsl.com>; Wed, 30 Aug 2023 09:36:06 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.103
X-Spam-Level:
X-Spam-Status: No, score=-2.103 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, HTML_MESSAGE=0.001, MIME_QP_LONG_LINE=0.001, RCVD_IN_ZEN_BLOCKED_OPENDNS=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, T_SCC_BODY_TEXT_LINE=-0.01, URIBL_BLOCKED=0.001, 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 (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 WS8-oQaE4eT1 for <dhcwg@ietfa.amsl.com>; Wed, 30 Aug 2023 09:36:02 -0700 (PDT)
Received: from mail-yb1-xb30.google.com (mail-yb1-xb30.google.com [IPv6:2607:f8b0:4864:20::b30]) (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 CE02CC15155B for <dhcwg@ietf.org>; Wed, 30 Aug 2023 09:36:02 -0700 (PDT)
Received: by mail-yb1-xb30.google.com with SMTP id 3f1490d57ef6-d7cbcfdf137so535556276.2 for <dhcwg@ietf.org>; Wed, 30 Aug 2023 09:36:02 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20221208; t=1693413362; x=1694018162; darn=ietf.org; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=rmiD1MQewFNdYuesUT/uHr/uZz8TBc/lRJG7CbQjROU=; b=bRNI6eXHPF/87xKsXfPby4OdtcPTZ9Cib4XKkDByLkDW6XAS1g2w7OZzdpRKiJUHEP Shj9yCfYyaFuy4XPBrbVB0XdpGiKyCaIb3iuSWwQqxop/A76mH4wJgIEI0WmFMpSBc3/ dwuN3rPEZvWy2iulkTYVbk5dXzR5EMIdLxeC3P3op8rLktVxwu8yaCizSNLOeNidVy64 D9/7ebRqwduXU33HDzt8AN8Xx4lsbS6lPay1KqXVYF2yAEZf7hQ2oBrbgtEwV9I5LTgz zCNTb9HcUf9pHgPt6B3RaCiWyNHGahZG7ZVdhkSWlE3wiKBFVZsQTqJiAF4GptG04pGN 9NfA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1693413362; x=1694018162; h=to:in-reply-to:cc:references:message-id:date:subject:mime-version :from:content-transfer-encoding:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=rmiD1MQewFNdYuesUT/uHr/uZz8TBc/lRJG7CbQjROU=; b=fcM2i/ShWSqeCMcvD3BeWRnLQf9gBP4E7ji8FhaSKBCh0I0qsaXbD9VGXOkS63mDQl 22TbwYeF1xlWSwQ6JpJq3VvmxN35HJHOErdHSBMBReImd673hTzZU6U82gOa2+YpE1lZ gnCGQaQREPQHce1ICoSQYGvxGebWcjdbWl2OOegE94anfY5FfsvUPD8lt/V26fMFOwLN 7F1zj3FWN4yrFniTjhvqyTDyiefUXCqsg9j/4gfeWki1uN5Ch54J9h1K5rm+th9E85li J35u6X0UKkl8ZeEZ3jyyFdWneWoo0HxpEmgLiqMYZml1Ht/pf1llYjmseW8txf4LhO/P EtCA==
X-Gm-Message-State: AOJu0YxyQs77lHOW2ftoICYjBz5IjE2+dqCVopHnXOafJhhotzAHgyNq Hlw7ucFXSk2vVYaIbTmdqg==
X-Google-Smtp-Source: AGHT+IFyO/8Xuz/Rkl/xd2E1bMU1yIstI4Nj5noi7AniJiLY1KTTVBt+pfdb7KpBuPjg8ujEsFBp7g==
X-Received: by 2002:a25:fe09:0:b0:d62:a199:fb18 with SMTP id k9-20020a25fe09000000b00d62a199fb18mr2503049ybe.60.1693413361942; Wed, 30 Aug 2023 09:36:01 -0700 (PDT)
Received: from smtpclient.apple (d-24-233-121-124.nh.cpe.atlanticbb.net. [24.233.121.124]) by smtp.gmail.com with ESMTPSA id eh15-20020a05622a578f00b003f7fd3ce69fsm3825261qtb.59.2023.08.30.09.36.01 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 30 Aug 2023 09:36:01 -0700 (PDT)
Content-Type: multipart/alternative; boundary="Apple-Mail-555C3810-15D8-4415-83B9-1E26A41ADA16"
Content-Transfer-Encoding: 7bit
From: Bernie Volz <bevolz@gmail.com>
Mime-Version: 1.0 (1.0)
Date: Wed, 30 Aug 2023 12:35:50 -0400
Message-Id: <29B0C260-CB17-4DAD-916B-60EF11FE041F@gmail.com>
References: <PA4PR07MB7568738924CB7A293378D8B387E6A@PA4PR07MB7568.eurprd07.prod.outlook.com>
Cc: tim@qacafe.com, dhcwg@ietf.org, bharat_joshi@infosys.com, kurapati@juniper.net, Siddharth Sharma <siddharth.sharma@ericsson.com>
In-Reply-To: <PA4PR07MB7568738924CB7A293378D8B387E6A@PA4PR07MB7568.eurprd07.prod.outlook.com>
To: Claudio Porfiri <claudio.porfiri@ericsson.com>
X-Mailer: iPad Mail (20G75)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/xc-FL_qL_S9xKeZMdKWm5CUDdw8>
Subject: Re: [dhcwg] L2RA
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.39
Precedence: list
List-Id: Dynamic Host Configuration <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/dhcwg/>
List-Post: <mailto:dhcwg@ietf.org>
List-Help: <mailto:dhcwg-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 30 Aug 2023 16:36:06 -0000

Hi:

You are always “free” to submit an individual draft. We would need to start the draft process over at the “beginning” (individual draft, discuss, submit for adoption, …) as 11 years ago is a long period of inactivity and doesn’t make sense to just pickup where it left off.

Whether the WG will have interest or not remains to be seen.

It is worth to research as to why it was dropped - especially if it was for technical reasons that could not easily be overcome - rather than just loss of interest because of no good applicablity of the technology to real world scenarios (assuming there may now be some).

Though I will add that given the 30+ years that DHCPv4 has been around, the bar may be set high to add this now?

- Bernie Volz

> On Aug 30, 2023, at 9:44 AM, Claudio Porfiri <claudio.porfiri@ericsson.com> wrote:
> 
> 
> Hi Bernie and Timothy,
> We have recently found a new scenario driven by O-RAN and CPRI specifications where a L2 ethernet switch needs a L2 Relay Agent with DHCPv4.
> There’s no IETF definition of that scenario, but a draft exists https://datatracker.ietf.org/doc/html/draft-ietf-dhc-l2ra-06 expired 11 years ago that was aimed at describing L2RA.
> The existing rfc6221 has a reference to the L2RA work and even Broadband Forum’s TR-101 complains that a L2RA didn’t exist.
> Do you think that is possible to resume that draft and proceed forwards, or even include the L2RA specific parts in a new revision of rfc3046?
>  
> Thanks and best regards,
> Claudio Porfiri