Re: [dhcwg] [EXTERNAL] Re: [v6ops] Re: Question to DHCPv6 Relay Implementors regarding draft-ietf-dhc-dhcpv6-pd-relay-requirements

Ted Lemon <mellon@fugue.com> Tue, 13 October 2020 18:42 UTC

Return-Path: <mellon@fugue.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 8A47D3A0FC4 for <dhcwg@ietfa.amsl.com>; Tue, 13 Oct 2020 11:42:33 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.898
X-Spam-Level:
X-Spam-Status: No, score=-1.898 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=unavailable autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=fugue-com.20150623.gappssmtp.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OfxpTpd0G7GI for <dhcwg@ietfa.amsl.com>; Tue, 13 Oct 2020 11:42:32 -0700 (PDT)
Received: from mail-io1-xd2a.google.com (mail-io1-xd2a.google.com [IPv6:2607:f8b0:4864:20::d2a]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E2E063A0FC3 for <dhcwg@ietf.org>; Tue, 13 Oct 2020 11:42:31 -0700 (PDT)
Received: by mail-io1-xd2a.google.com with SMTP id q25so753223ioh.4 for <dhcwg@ietf.org>; Tue, 13 Oct 2020 11:42:31 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:mime-version:subject:date:in-reply-to:cc:to :references; bh=nmg+rrkkxqGpa7sZPlJtXEj3GvQq4qN8DBlFuNc8x3c=; b=XAol0xTflnw6tKwyp/AY76NjNzXzXMt6gt5Gdkm39klEEyw8Pbo7dYQEfRIviBHpSF QH+N+DHDb5Oo0G+5UyxWTr3wrsfN/PiAOjF1zkKbZaOt0NAmwy4ScQsbcLtamEkdBwBN nxXVDOtOAgIyEiKm9Nn+kr8sUtp/p4/TwWhyfrvQlfhvHnh8uCk4rAmSXIxGGXJfgyqB 4yn/8HN9GRCUxDsl9jrA2LbvgS3h0WhI9rHobqOK4heCNiBBX74Rdrstr/NAvpCHuVSo +G7iLzUddZ1rUQbaqIF9WRSe3BkKdx24wjwSnbc0AUvar8zLia50yS5GHoTB64us6cHs 5tuA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:message-id:mime-version:subject:date :in-reply-to:cc:to:references; bh=nmg+rrkkxqGpa7sZPlJtXEj3GvQq4qN8DBlFuNc8x3c=; b=QNczH9uN/uTBvMHxVl/rUiqu7HZ6UmbOpEC8fHoRZFnQQZSsY/SNg482saCw1DKRSd rwoiKcioJhVEWvcNnhIPW3igLH+78KjMRn9CwqaeKOhAgCmSaIm+eLCDdMiEeUJcdu9+ ryWFkko7VINQHl5pHj4h6b/V8W6yYDt0dbN6VGpD+sI09ySi2pcaOPsPYk/oOgh8E7DZ OqRPyJGKW9x58y+zpxYun8fb6/uZXMhWkMpvL2VGo794sbeV9CMxZdS4K6Zwu0CfsSI/ iOF5KN46/SrNZd2zhEF2cdd072GCapcwjMAGyQTomYV7yP6zhcY6fYndTlc8FG1xAGtj 6HeA==
X-Gm-Message-State: AOAM533wayXEceyJSLwFAGf2IiAB13djodZpkzFA6KImWEzn16aSSLvh y4RbsuQku1uy9wMI6dG9USxq3w==
X-Google-Smtp-Source: ABdhPJzKJc34hVgw9K98TXeelIUXpC/tE70lklUtVpQSUA7LNUaF7UqyPHtyDrTQknvGeZ6sAoYzMw==
X-Received: by 2002:a6b:b2c5:: with SMTP id b188mr178559iof.90.1602614551136; Tue, 13 Oct 2020 11:42:31 -0700 (PDT)
Received: from mithrandir.lan (c-24-91-177-160.hsd1.nh.comcast.net. [24.91.177.160]) by smtp.gmail.com with ESMTPSA id o72sm687310ilb.6.2020.10.13.11.42.29 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Tue, 13 Oct 2020 11:42:30 -0700 (PDT)
From: Ted Lemon <mellon@fugue.com>
Message-Id: <9944583D-57D2-47D8-9A35-F5E9BCA3EE11@fugue.com>
Content-Type: multipart/alternative; boundary="Apple-Mail=_3C074FA9-8B7B-4741-996D-4C54F72C398A"
Mime-Version: 1.0 (Mac OS X Mail 14.0 \(3654.0.3.2.82\))
Date: Tue, 13 Oct 2020 14:42:29 -0400
In-Reply-To: <9428b888a7c046a38f85de8fcc260857@boeing.com>
Cc: Michael Richardson <mcr+ietf@sandelman.ca>, "ianfarrer@gmx.com" <ianfarrer@gmx.com>, Jen Linkova <furry13@gmail.com>, dhcwg <dhcwg@ietf.org>, v6ops list <v6ops@ietf.org>, 6man <ipv6@ietf.org>
To: "Templin (US), Fred L" <Fred.L.Templin@boeing.com>
References: <5f119ffbb67245a9b9d34a0d8f7398f4@boeing.com> <10487.1602608586@localhost> <378d3420690246bbae253fb15be8c9a7@boeing.com> <4478E969-8C25-46E1-9C21-B74189F23058@fugue.com> <9428b888a7c046a38f85de8fcc260857@boeing.com>
X-Mailer: Apple Mail (2.3654.0.3.2.82)
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/AQA5D-m1L6dOMrFM0zSRJFVxYyI>
Subject: Re: [dhcwg] [EXTERNAL] Re: [v6ops] Re: Question to DHCPv6 Relay Implementors regarding draft-ietf-dhc-dhcpv6-pd-relay-requirements
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: <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: Tue, 13 Oct 2020 18:42:34 -0000

On Oct 13, 2020, at 2:38 PM, Templin (US), Fred L <Fred.L.Templin@boeing.com <mailto:Fred.L.Templin@boeing.com>> wrote:
> Think of the L2 proxy as a middlebox that occurs between the client and the relay (even
> for the RFC6221 LDRA case). The client is on a “downstream link segment” of the proxy,
> and the relay is on an “upstream link segment” of the proxy. When the LDRA running in
> the same physical box as the relay gets the DHCPv6 Solicit message, the link-layer source
> address it will see is ‘P’ (i.e., the upstream link segment address of the proxy).

If it’s an LDRA, and that’s the behavior, it’s not following the RFC. I can’t speak to other types of proxies, of course.