IETF Logo Mail Archive

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

神明達哉 <jinmei@wide.ad.jp> Thu, 18 August 2016 22:54 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 F3C0412D7AA for <dhcwg@ietfa.amsl.com>; Thu, 18 Aug 2016 15:54:06 -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 ABhKHvnDg19T for <dhcwg@ietfa.amsl.com>; Thu, 18 Aug 2016 15:54:05 -0700 (PDT)
Received: from mail-qt0-x22c.google.com (mail-qt0-x22c.google.com [IPv6:2607:f8b0:400d:c0d::22c]) (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 3456012D1E4 for <dhcwg@ietf.org>; Thu, 18 Aug 2016 15:54:05 -0700 (PDT)
Received: by mail-qt0-x22c.google.com with SMTP id x25so3743655qtx.2 for <dhcwg@ietf.org>; Thu, 18 Aug 2016 15:54:05 -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=Tagli+nyKOU8aor7Vqh/CwjpZRBWluTYiN7KR7gJyuo=; b=qf0DiOgzq8Ni6epeASdVk+zDEr7bR5lDA52KqBgcKUMYgZ1WwKmwSFjAg1YIbqNkOh uK5yAl++SydlOfBKXBPF5NVl2jyompCaW2bLVB8WhMrHiDtJYdV6x4nnAnDooS9HP0qL GJphvZG3Hi1bsvFs2oPOCuQ6puBwcpN2CW95VCr2KDdP6J2/KCPRApX8+NuRtRGylHcx 91au4yAJQ5k+tBCiry/4ieSpda46O36p/WOGFCMcMRkXDAbd1RZkrtsQ87pYQtH7YR8i 7vNnm9hBNw975wB10jUvwKpF7Ukg0Ox8fSnegnQ1kXa/0IXpBEWrL38CStqFisLifIT7 RrFg==
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=Tagli+nyKOU8aor7Vqh/CwjpZRBWluTYiN7KR7gJyuo=; b=f1Igwp+D46C98s9liHCdnUqOo0zZpmP9gJZ2iPS7bDCrKlzZc5Wx2bSJd0sNpNWs14 Hbo7Aehrxb7BCaucJ8vcikZGy1bmfMZ7BqgmzubLJmZswMM34r+TcnOx9+84BKVzeEAT NBLEts5B9vl/zI0+SpZ9DcCQ8p37vH5OIsuCPXVqbbcqj2wb3VLItIlQhw6w+W21NOcI 4i5jREpqKqsB0bbNR0J1FxcHj5yEkY+YBgXSwcaY9vLIypNFtYPyWPOWE5vDiL1i54yv JvuESWDn9ABn29TCloOZLcv3drW9NQDEtRKWXYwNme+w4UH6j1o3+LjlX3lm0fHsUBR5 3s/Q==
X-Gm-Message-State: AEkoous2ImEe2NKxTuj6oxv2QZfBHbosl5P//GoRBfshmzLsZ5l8X5/lNyzWw119f2/DjT6ocoeuCrpKrnenMA==
X-Received: by 10.200.48.146 with SMTP id v18mr5532804qta.107.1471560844372; Thu, 18 Aug 2016 15:54:04 -0700 (PDT)
MIME-Version: 1.0
Sender: jinmei.tatuya@gmail.com
Received: by 10.237.33.154 with HTTP; Thu, 18 Aug 2016 15:54:03 -0700 (PDT)
In-Reply-To: <5ec83aaf4e76497aa4b4d465483bdcf5@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>
From: 神明達哉 <jinmei@wide.ad.jp>
Date: Thu, 18 Aug 2016 15:54:03 -0700
X-Google-Sender-Auth: 0_fQwbpZLsXZqo4cLeyd11DKG3g
Message-ID: <CAJE_bqeKqEgLVC2ZZyUCjsrPP5_suRJ8en2NC+g13Q5PyQL1iw@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/XNsGq37bbh6ctAhIjbucsWbBWxc>
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 22:54:07 -0000

At Thu, 18 Aug 2016 22:42:38 +0000,
"Templin, Fred L" <Fred.L.Templin@boeing.com> wrote:

> Hi, I already made a stronger case as follows:
>
> > 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.

To me, it just looks like "in some cases encryption may not be needed"
and not so different from "it's overkilling for me", so not very
convincing to overturn a wg consensus on always enabling encryption.
But it's ultimately up to the wg.

--
JINMEI, Tatuya

v2.23.0 | Report a Bug | By Email