IETF Logo Mail Archive

Re: [dhcwg] Citing 'draft-ietf-dhc-secdhcpv6' (rfc3315bis)

神明達哉 <jinmei@wide.ad.jp> Thu, 18 August 2016 00:25 UTC

Return-Path: <jinmei.tatuya@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 24F5B12D61D for <dhcwg@ietfa.amsl.com>; Wed, 17 Aug 2016 17:25:46 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.598
X-Spam-Level:
X-Spam-Status: No, score=-2.598 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, FREEMAIL_FORGED_FROMDOMAIN=0.001, FREEMAIL_FROM=0.001, HEADER_FROM_DIFFERENT_DOMAINS=0.001, RCVD_IN_DNSWL_LOW=-0.7, SPF_PASS=-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 ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id N2HLADIeulrn for <dhcwg@ietfa.amsl.com>; Wed, 17 Aug 2016 17:25:44 -0700 (PDT)
Received: from mail-qk0-x241.google.com (mail-qk0-x241.google.com [IPv6:2607:f8b0:400d:c09::241]) (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 AD46812D1EB for <dhcwg@ietf.org>; Wed, 17 Aug 2016 17:25:44 -0700 (PDT)
Received: by mail-qk0-x241.google.com with SMTP id o1so586706qkd.2 for <dhcwg@ietf.org>; Wed, 17 Aug 2016 17:25:44 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:from:date:message-id :subject:to:cc; bh=LyUT3G2+ITS2abJayMUErEe6CmZTliz6jmxxHjL1gDE=; b=PMQZCgLcGMRlqQL7OAQZr3AzS6lA5D/AzwCyQln6QjcQ9m2zI4HTyCu0y5778GPzOu Ks5oQmYf1eyV8TbSvtw5nQfconPUYvH9v+BTsOyjSZU+Lc2yEfIRoyFqk0SBe+1JNepC Jl5QMrWZPl9iKZ8GgU35DtQftXRSVyXlkp3CcWVoc9aeBBs31AOFa7h72Kr7YSj3K0oB uQlyfms5+YvBSyH2/Havxw6gHS1ltp0AyedUPdoAEDXM4XrJ4mJOt9sxbZX57WrhgLIF dtR/YTvSmBvfmjvZjawjZT02qo2QP8CUeRZk8wb6LstGkZhMpqC2NILAsW6q1WaurJAw Hy3g==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:from :date:message-id:subject:to:cc; bh=LyUT3G2+ITS2abJayMUErEe6CmZTliz6jmxxHjL1gDE=; b=DKFCZeShPoW7BI3skOuypEArIrGriMm+rZOV57JxqBn1iHFc8Pikzwk/txYvQwRP/6 xXUCeLRRox6cGGyHe7y9krOUkqjAfdKKPZGbX3UInxwYKgAPxs20L87PVT4uqkbxNTz/ msuLN4QoN+xd6braW5pvYYMo8Mu0ZnAFySFD6+XwopQUjZ5Vmx3xdFfjCdApt1xHfl7o l03kwKSMfgTQaQ7exCp+F1/ge+ZlHgpY/hJu2xEkQwoERolfQ6c1YQLRq525yUMirSXG +c4v9m5JJnznqcSUvT9UBWRm0JCw3s1fzOmZmfvmQkWShFrsD+w7peWRlgBcakweB4rv afiw==
X-Gm-Message-State: AEkoout6cTZiK/YqXOQqsBE8IsqLE9/uvsvvzYJ9bf9vGTWqQ8vu0t2iK6lPCKecHUXH1rurSqz5pbnPxlfiTQ==
X-Received: by 10.55.104.139 with SMTP id d133mr46398363qkc.126.1471479943627; Wed, 17 Aug 2016 17:25:43 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.33.154 with HTTP; Wed, 17 Aug 2016 17:25:43 -0700 (PDT)
In-Reply-To: <b65e1dd66b634240b3ca164b2c04c20a@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>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Wed, 17 Aug 2016 17:25:43 -0700
X-Google-Sender-Auth: cEXugxtD0q5Ne-oYlorAAV-o-oM
Message-ID: <CAJE_bqfb5sxOpkTEXkwZXckKBWof7U1-W6EFzCHk7ijnMjpMMA@mail.gmail.com>
To: "Templin, Fred L" <Fred.L.Templin@boeing.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/rPS1mEIw5eXNRKpePD9ujmc0oPg>
Cc: "<dhcwg@ietf.org>" <dhcwg@ietf.org>, Francis Dupont <Francis.Dupont@fdupont.fr>, "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, 18 Aug 2016 00:25:46 -0000

At Tue, 16 Aug 2016 21:35:34 +0000,
"Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:

> I glanced through the document, and my first impression is that it has become
> overkill for what I need. For my needs, there is already link-layer security and
> so I do not need encryption between the client and server.
[...]
> I think what that means in terms of this draft is that for some use cases all
> that is needed is for the client to include a Signature option in its DHCPv6
> messages to the server. The client does not need to include a Certificate
> option nor any encryption options. So, I would like it if the draft could
> include a simple "authentication only" mode of operation.

The currently described approach is based on a WG consensus made at
the Yokohama IETF last November.  So you'll need a stronger argument
than "it's overkill for me" if you want to change that.

--
JINMEI, Tatuya

v2.23.0 | Report a Bug | By Email