[dhcwg] Fwd: New Version Notification for draft-ietf-dhc-sedhcpv6-20.txt

Lishan Li <lilishan48@gmail.com> Mon, 16 January 2017 09:10 UTC

Return-Path: <lilishan48@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 5D1161293E9 for <dhcwg@ietfa.amsl.com>; Mon, 16 Jan 2017 01:10:30 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Level:
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_ENVFROM_END_DIGIT=0.25, FREEMAIL_FROM=0.001, HTML_MESSAGE=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 vTQbshZ-JB5C for <dhcwg@ietfa.amsl.com>; Mon, 16 Jan 2017 01:10:28 -0800 (PST)
Received: from mail-qt0-x236.google.com (mail-qt0-x236.google.com [IPv6:2607:f8b0:400d:c0d::236]) (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 111551293E4 for <dhcwg@ietf.org>; Mon, 16 Jan 2017 01:10:27 -0800 (PST)
Received: by mail-qt0-x236.google.com with SMTP id l7so98884573qtd.1 for <dhcwg@ietf.org>; Mon, 16 Jan 2017 01:10:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to; bh=QKWz1gTtZcsCExP3bHz67yXZNuTONWHaT1GpEV7qQJY=; b=nHRmzN3OTSa8xVTj7hcq5Aj4MYATBSF/FErJANQaTY51hwRQKNndND/Lu8spd2fJfC klfKlZnDKk4YnJBVeizNRLqy6R5ChXGwLV4FTM8hPriqCCRdFiqdxDQ5K8t3rq2Gu8Jp /Zs6mEsxCVvL2582+EiK7WNX/PyL/fA5xhyIHsaRauwuqWytloL3OYLBjVj0zjaLh+Tk /ahDoZV5UdPcpsyijpYAhqmvgIoOLUGwMm0SyvlMwYluerWBGefbocrKfESQi1XBzT+P 9ferhkMBl59AKsaBrL+7zJLRbtR5hWLSaZFP/a85Mh0gjzt4sMQRkCR3k6OzhjVwWUyC UFpA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to; bh=QKWz1gTtZcsCExP3bHz67yXZNuTONWHaT1GpEV7qQJY=; b=heZLTZfyzRJyp+jaZ9R52ldWkRq72a5+R8LmjTt26z0YZKCSWU5WHLJD/kUxYwB4mr EmVB8mLUYHBW+xSBVrkcOI+fnEzs+MVeCNFfI3ScpNiJ6q+NDOE4xkG45PynCDyjdgNK L3T1+C/JS/QvTOnMajTlhJqn14VhX6MW/JimjWQ6v+NO3tQBY+QtWeltlhvP5mz+P1mZ yGALYo4q99734+vxAqGunnZYIKjKQ57NJTDQxBiRc65lttkk+2xkU9mmp7EwiV5Lg19E SljSyPVyDD66QcmAHYJf5HyLC78W16cxFhCZBLmL0hJRXAR5J4sGphNDpHoe4d1mvNFl k+Zg==
X-Gm-Message-State: AIkVDXIe0QU840I/KsAFf+YgscaTYPLoPoDhvvYjGGUuYpx0BujRjlz5qVxoVr327FeEkXGndn3+E/THCZPa2w==
X-Received: by 10.200.37.22 with SMTP id 22mr16109884qtm.250.1484557826769; Mon, 16 Jan 2017 01:10:26 -0800 (PST)
MIME-Version: 1.0
Received: by 10.237.36.117 with HTTP; Mon, 16 Jan 2017 01:10:26 -0800 (PST)
In-Reply-To: <148455739520.22478.14651605359463322132.idtracker@ietfa.amsl.com>
References: <148455739520.22478.14651605359463322132.idtracker@ietfa.amsl.com>
From: Lishan Li <lilishan48@gmail.com>
Date: Mon, 16 Jan 2017 17:10:26 +0800
Message-ID: <CAJ3w4NdCk8CBfNagcXT_VW_50+=xK=N7aB5HHqqn3stMt7Gy-Q@mail.gmail.com>
To: dhcwg <dhcwg@ietf.org>
Content-Type: multipart/alternative; boundary=001a11427f8ee9ea7c0546328d99
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/UhhX8wS9SWASf0o2nGPaxh9PMRs>
Subject: [dhcwg] Fwd: New Version Notification for draft-ietf-dhc-sedhcpv6-20.txt
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: Mon, 16 Jan 2017 09:10:30 -0000

Dear All,

We have submitted a new version of secure DHCPv6. Thanks a lot for Bernie's
valuable comment.
In this version, we made the following update:
1. In client behavior part, we adds some description about opportunistic
security. In this way, in some scenario, authentication is optional.
2. Add the reference of RFC 4034 for the encryption key tag calculation.
3. Delete the part that the relay agent cache server announcements part.
4. Add the assumption that the client's initial stored increasing number is
set to zero. In this way, for the first time increasing number check in the
Reply message, the check will always succeed, and then the locally stored
number is changed into the contained number in the Reply message.
5. Correct many grammar mistakes.

Looking forward to your review and guidance. Thanks in advance.

Best Regards,
Lishan

---------- Forwarded message ----------
From: <internet-drafts@ietf.org>;
Date: 2017-01-16 17:03 GMT+08:00
Subject: New Version Notification for draft-ietf-dhc-sedhcpv6-20.txt
To: Ted Lemon <ted.lemon@nominum.com>;, Tatuya Jinmei <jinmei@wide.ad.jp>;,
Sheng Jiang <jiangsheng@huawei.com>;, Dacheng Zhang <dacheng.zhang@gmail.com>;,
dhc-chairs@ietf.org, Lishan Li <lilishan48@gmail.com>;, Yong Cui <
yong@csnet1.cs.tsinghua.edu.cn>;, Ted Lemon <Ted.Lemon@nominum.com>;



A new version of I-D, draft-ietf-dhc-sedhcpv6-20.txt
has been successfully submitted by Lishan Li and posted to the
IETF repository.

Name:           draft-ietf-dhc-sedhcpv6
Revision:       20
Title:          Secure DHCPv6
Document date:  2017-01-16
Group:          dhc
Pages:          31
URL:            https://www.ietf.org/internet-drafts/draft-ietf-dhc-
sedhcpv6-20.txt
Status:         https://datatracker.ietf.org/doc/draft-ietf-dhc-sedhcpv6/
Htmlized:       https://tools.ietf.org/html/draft-ietf-dhc-sedhcpv6-20
Diff:           https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-sedhcpv6-20

Abstract:
   DHCPv6 includes no deployable security mechanism that can protect
   end-to-end communication between DHCP clients and servers.  This
   document describes a mechanism for using public key cryptography to
   provide such security.  The mechanism provides encryption in all
   cases, and can be used for authentication based on pre-sharing of
   authorized certificates.




Please note that it may take a couple of minutes from the time of submission
until the htmlized version and diff are available at tools.ietf.org.

The IETF Secretariat