Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
Ted Lemon <mellon@fugue.com> Thu, 25 August 2016 18:14 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 9AA9A12D162 for <dhcwg@ietfa.amsl.com>; Thu, 25 Aug 2016 11:14:37 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.9
X-Spam-Level:
X-Spam-Status: No, score=-1.9 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham 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 H0whj8ttdO2e for <dhcwg@ietfa.amsl.com>; Thu, 25 Aug 2016 11:14:35 -0700 (PDT)
Received: from mail-lf0-x229.google.com (mail-lf0-x229.google.com [IPv6:2a00:1450:4010:c07::229]) (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 444C912D5F8 for <dhcwg@ietf.org>; Thu, 25 Aug 2016 11:14:34 -0700 (PDT)
Received: by mail-lf0-x229.google.com with SMTP id b199so40522353lfe.0 for <dhcwg@ietf.org>; Thu, 25 Aug 2016 11:14:34 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=fugue-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=jG2OKQ1IkFvrTqwPXCHjD/pZDLfJuE4Cd9KAoBfoIeA=; b=bvDedP7Uj0Q5rlzQvj9ufJV5xhqOGdZjFFP6GEtQ8DUxxoe7idNNZdtdZRw2nUK+Ub uIGjOXLztL/ntE2byfk0OQlnQXFxMRBu4qMSIXpF1/kZFI4XlBNPjFYz890P91lvLNjs 6qkuzDfvGFps05ckogmB3ym1EeFrF2mdEtOpvb9URZzHYA5uALoB7F81dAg8DUjmj4d7 wz1POIIi6oWB3tC4w2kOObs9olRCUtIuQsNz/HeyqZIzoBbU6yLp3Tk5WjXQSfrXAVBF aNvm2X4dhETkb6FrEhISQ5Ek4tkQ9sONef/rd/pkeK1cD295BP4xlML0IGdT2gbrXDjQ hn/g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=jG2OKQ1IkFvrTqwPXCHjD/pZDLfJuE4Cd9KAoBfoIeA=; b=Tdm+4y6wtTIQXgt+BgIQWb4d6HY14DZTsFB2xD0UTupofvQPus0Gcqr0chU4Fld6Nv o2QvENmDIXd7cL7/+5S70aI4JkkhtQ/fTjDOPbCAgteXcbIuUW5myR9VZw70D3wbR3E4 yoSKN5GFcWdpC4wrts7XzKBax8PtMO8K4sf51lPB+Y8Be0KCczEizoufGV86418WqJdJ ckyb2CzIbnql84igaaI/ZZpMBCkE7AdAP4UeFsE0C5yuO0lIFa+Y1rF13I3hBNHi3Smw xzYRYZTnut3gKVm+MhD4mtaFYGysUgaI+KtYI6cJjCHdHmPfvRYmXj58eIf3rPwKWp/K ydBw==
X-Gm-Message-State: AE9vXwOEOkctN/zXBHerV4y0nfembirDk9E76ft0bxpEoWJotmLuiOtFLVpnwtloJKh4mxAjeWC+wbNFHRSNGg==
X-Received: by 10.25.131.150 with SMTP id f144mr2522845lfd.53.1472148872228; Thu, 25 Aug 2016 11:14:32 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.25.217.93 with HTTP; Thu, 25 Aug 2016 11:13:51 -0700 (PDT)
In-Reply-To: <d6f8ed9bdfc8461aa463e6542269ccda@XCH15-05-05.nw.nos.boeing.com>
References: <92dcf2e0cf08452caa5861f7258ea6c5@XCH15-05-05.nw.nos.boeing.com> <201608121919.u7CJJqcS056876@givry.fdupont.fr> <c5303eef3c124228825f32a40f229107@XCH-ALN-003.cisco.com> <ccaff4d4cb5c4eefb05eee0660c2611c@XCH15-05-05.nw.nos.boeing.com> <f46aa91e4cfb41b29dd2d8186f5959f8@XCH-ALN-003.cisco.com> <ba1c8ff573d7466b8c437373e05f1023@XCH15-05-05.nw.nos.boeing.com> <b65e1dd66b634240b3ca164b2c04c20a@XCH15-05-05.nw.nos.boeing.com> <CAJE_bqfb5sxOpkTEXkwZXckKBWof7U1-W6EFzCHk7ijnMjpMMA@mail.gmail.com> <5ec83aaf4e76497aa4b4d465483bdcf5@XCH15-05-05.nw.nos.boeing.com> <CAJE_bqeKqEgLVC2ZZyUCjsrPP5_suRJ8en2NC+g13Q5PyQL1iw@mail.gmail.com> <30c9413c4662476096ef087ac88f6314@XCH-ALN-003.cisco.com> <dc9d2c300d574732a12f7f366f6223c0@XCH15-05-11.nw.nos.boeing.com> <3A5F0B79-8C76-4E82-97E9-FA63657DE6C3@cisco.com> <CAJ3w4NdjgVxvnvuaWjGM=qtOe0qUq4N96fVXsbNrf=YkhiABbQ@mail.gmail.com> <2f45b99b50f84b1280e92ad824e39e26@XCH15-05-05.nw.nos.boeing.com> <9E9A9543-ECB0-4D99-A00F-1AAD813B6522@fugue.com> <091180442e44490ba451874d1543f814@XCH15-05-05.nw.nos.boeing.com> <CAPt1N1=pD7TBrU_NnuyGz61+CiUVp0JiyLLfMUKTz_dgnO59QQ@mail.gmail.com> <AF387F3E-1B64-4E5D-BAF7-EB5BF3ED1EB4@cisco.com> <55dcbc0cd1484fffa264b18b2fc3322c@XCH15-05-05.nw.nos.boeing.com> <122453F6-3987-46D4-89EB-84AF99402BC3@cisco.com> <dd827ec92b874ad8a188b17f44392c54@XCH15-05-05.nw.nos.boeing.com> <438d610f19da4f7aa39fb70a7dc11513@XCH15-05-05.nw.nos.boeing.com> <2279C5E3-0D51-4631-AFC9-DAF05339D21D@cisco.com> <d6f8ed9bdfc8461aa463e6542269ccda@XCH15-05-05.nw.nos.boeing.com>
From: Ted Lemon <mellon@fugue.com>
Date: Thu, 25 Aug 2016 14:13:51 -0400
Message-ID: <CAPt1N1nTHJm44KR1SBg=ohj8HfKO+yLna+b+95FPocTjcuuwbQ@mail.gmail.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: multipart/alternative; boundary="001a113f20b8960a0a053ae95e68"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/wgWWIXkiNUYIe47581yjtlq8YXI>
Cc: dhcwg <dhcwg@ietf.org>, "Bernie Volz (volz)" <volz@cisco.com>
Subject: Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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: Thu, 25 Aug 2016 18:14:37 -0000
Fred, if we allow a non-encrypted mode, that will be the only mode that is universally implemented. That is why the consensus was to only define a standard for the encrypted mode. You are asking us to compromise rather drastically on that for the benefit of your protocol, which as far as I know has no real-world deployments that require interop, and is not on track to become a standard. I don't mean to say that what you want doesn't matter, but neither is it the case that you have said anything to justify overturning the working group consensus on this. So instead, the right thing to do is to figure out a way to get what you want without requiring the working group to change its consensus. If what you want is for the client to be able to communicate preferences to the relay, something similar to the relay-supplied options option would do the trick, only sent from the client rather than the relay. On Thu, Aug 25, 2016 at 2:08 PM, Templin, Fred L <Fred.L.Templin@boeing.com> wrote: > Hi Bernie, > > > > VPN clients may need to configure their virtual interfaces over multiple > > underlying physical interfaces (e.g., WiFi, Cellular, SATCOM, etc.) – each > > with its own IP address. The relay then sees the client as a single network > > layer entity with multiple link-layer addresses. So, the client needs to > > have some way to tell the relay about its preferences for each of the > > underlying interfaces. The client does this by including an option with the > > preference values that the relay then needs to snoop in-the-clear, > > i.e., and not encrypted. > > > > Thanks – Fred > > fred.l.templin@boeing.com > > > > *From:* Bernie Volz (volz) [mailto:volz@cisco.com] > *Sent:* Thursday, August 25, 2016 9:41 AM > *To:* Templin, Fred L <Fred.L.Templin@boeing.com> > *Cc:* dhcwg <dhcwg@ietf.org>; Ted Lemon <mellon@fugue.com> > *Subject:* Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis) > > > > Please explain what else the relay needs to know. > > - Bernie (from iPhone) > > > On Aug 25, 2016, at 9:34 AM, Templin, Fred L <Fred.L.Templin@boeing.com> > wrote: > > Hi, on further consideration RAAN options alone are not sufficient for my > > needs. For my needs, the relay has to be able to inspect the contents of > > both the client’s messages to the server and the server’s messages to > > the client. And, it is about more than just IA_NA and IA_PD. > > > > The use case is VPN clients connecting in to a secured home network then > > using DHCPv6 to obtain prefixes and/or addresses. So, the client comes in > > across a secured link where there is no concern for eavesdropping, but > > the client still needs to prove to the server that it is authorized to > receive > > the requested addresses/prefixes. > > > > In that case, when we can say that the link is secured against > eavesdropping, > > then there is a use case for authentication-only DHCPv6 security. > > > > Thanks – Fred > > fred.l.templin@boeing.com > > > > *From:* dhcwg [mailto:dhcwg-bounces@ietf.org <dhcwg-bounces@ietf.org>] *On > Behalf Of *Templin, Fred L > *Sent:* Wednesday, August 24, 2016 12:51 PM > *To:* Bernie Volz (volz) <volz@cisco.com> > *Cc:* dhcwg <dhcwg@ietf.org>; Ted Lemon <mellon@fugue.com> > *Subject:* Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis) > > > > Can we dust this off and insert it back into the process? > > > > Thanks - Fred > > > > *From:* Bernie Volz (volz) [mailto:volz@cisco.com <volz@cisco.com>] > *Sent:* Wednesday, August 24, 2016 12:46 PM > *To:* Templin, Fred L <Fred.L.Templin@boeing.com> > *Cc:* Ralph Droms (rdroms) <rdroms@cisco.com>; Ted Lemon <mellon@fugue.com>; > dhcwg <dhcwg@ietf.org> > *Subject:* Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis) > > > > Note that latest version of that draft is https://tools.ietf.org/ > html/draft-ietf-dhc-dhcpv6-agentopt-delegate-04. > > > > Also, 03 used the https://tools.ietf.org/html/draft-ietf-dhc-dhcpv6- > srsn-option-02 draft to address out of order issues. Don't recall why 04 > removed this and whether there were other issues still unresolved - though > I think there were. > > > > Sadly there is no change log to indicate changes made in each rev, so we > will need to review the email dialog and meeting minutes around the time of > these drafts to determine open issues & how to move forward. I think > interest died because cable (cmts) just started to snoop the client > packets. This actually doesn't resolve out of order issues, though I think > those have not caused any known problems. So while in theory they could be, > in practice they are not. > > - Bernie (from iPhone) > > > On Aug 24, 2016, at 11:26 AM, Templin, Fred L <Fred.L.Templin@boeing.com> > wrote: > > draft-draft-droms-dhc-dhcpv6-agentopt-delegate-00.txt > >
- [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc331… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Francis Dupont
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Bernie Volz (volz)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Bernie Volz (volz)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… 神明達哉
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… 神明達哉
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Bernie Volz (volz)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Bernie Volz (volz)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Lishan Li
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Ted Lemon
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Ted Lemon
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Ted Lemon
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Ralph Droms (rdroms)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Bernie Volz (volz)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Bernie Volz (volz)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Ted Lemon
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Ted Lemon
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Ted Lemon
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Bernie Volz (volz)
- Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rf… Templin, Fred L