Re: [dhcwg] Questions about layer two relay agents in dhcpv4...

Ted Lemon <mellon@fugue.com> Mon, 16 August 2010 17:56 UTC

Return-Path: <mellon@fugue.com>
X-Original-To: dhcwg@core3.amsl.com
Delivered-To: dhcwg@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 0F32C3A6A11 for <dhcwg@core3.amsl.com>; Mon, 16 Aug 2010 10:56:03 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id s-PzMSRuJlyo for <dhcwg@core3.amsl.com>; Mon, 16 Aug 2010 10:56:02 -0700 (PDT)
Received: from toccata.fugue.com (toccata.fugue.com [204.152.186.142]) by core3.amsl.com (Postfix) with ESMTP id 6BBAD3A686B for <dhcwg@ietf.org>; Mon, 16 Aug 2010 10:56:01 -0700 (PDT)
Received: from [IPv6:2001::53aa:64c:0:1908:525d:2925] (unknown [IPv6:2001:0:53aa:64c:0:1908:525d:2925]) by toccata.fugue.com (Postfix) with ESMTPSA id A2EBE34E44CA; Mon, 16 Aug 2010 13:56:51 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v1081)
Content-Type: text/plain; charset="us-ascii"
From: Ted Lemon <mellon@fugue.com>
In-Reply-To: <4C695165.30704@cisco.com>
Date: Mon, 16 Aug 2010 13:56:34 -0400
Content-Transfer-Encoding: quoted-printable
Message-Id: <F5FD885F-24A7-416A-B3A4-D7D965DB6D06@fugue.com>
References: <8B2420CE-026D-465D-9256-B2DA76310CE1@fugue.com> <4C695165.30704@cisco.com>
To: Josh Littlefield <joshl@cisco.com>
X-Mailer: Apple Mail (2.1081)
Cc: "dhcwg@ietf.org Group" <dhcwg@ietf.org>
Subject: Re: [dhcwg] Questions about layer two relay agents in dhcpv4...
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <dhcwg.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/dhcwg>, <mailto:dhcwg-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/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: Mon, 16 Aug 2010 17:56:03 -0000

On Aug 16, 2010, at 10:55 AM, Josh Littlefield wrote:
> I do think this is a problem. TR-101, in which I participated in
> defining the L2RA requirements for EtherDSL, specifically requires the
> L2RA to remove option-82 from all packets:
>  [...]

Yes.

This is complicated by the fact that the l2ra draft is informational, not standards-track.   So essentially it just reports what people are doing with regards to l2ra, rather than specifying how to do l2ra.  I'm finding myself adding text to the relay agent encapsulation draft specifying how to do l2ra because of this.

Personally, I'd like to see the l2ra draft aimed at standards track, and specifying the correct way to do l2ra, rather than, as it does now, simply documenting various implementation strategies, some of which are clearly (to me!) broken.

I'm curious to know what the authors of the current draft think about this.   I'm pretty sure we've talked about this before, so I apologize for re-visiting well-trod ground, but I'm seeing the problem with new eyes now... :'}