[dhcwg] I-D Action: draft-ietf-dhc-relay-server-security-03.txt
internet-drafts@ietf.org Tue, 07 February 2017 15:45 UTC
Return-Path: <internet-drafts@ietf.org>
X-Original-To: dhcwg@ietf.org
Delivered-To: dhcwg@ietfa.amsl.com
Received: from ietfa.amsl.com (localhost [IPv6:::1]) by ietfa.amsl.com (Postfix) with ESMTP id 21EA3129422; Tue, 7 Feb 2017 07:45:34 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: internet-drafts@ietf.org
To: i-d-announce@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.42.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <148648233413.16188.1096005061921603374.idtracker@ietfa.amsl.com>
Date: Tue, 07 Feb 2017 07:45:34 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/Wyq4X0dif7HmfmQC3AZDlj7ofMY>
Cc: dhcwg@ietf.org
Subject: [dhcwg] I-D Action: draft-ietf-dhc-relay-server-security-03.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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, 07 Feb 2017 15:45:34 -0000
A New Internet-Draft is available from the on-line Internet-Drafts directories. This draft is a work item of the Dynamic Host Configuration of the IETF. Title : Security of Messages Exchanged Between Servers and Relay Agents Authors : Bernie Volz Yogendra Pal Filename : draft-ietf-dhc-relay-server-security-03.txt Pages : 8 Date : 2017-02-07 Abstract: The Dynamic Host Configuration Protocol for IPv4 (DHCPv4) has no guidance for how to secure messages exchanged between servers and relay agents. The Dynamic Host Configuration Protocol for IPv6 (DHCPv6) states that IPsec should be used to secure messages exchanged between servers and relay agents, but does not require encryption. And, with recent concerns about pervasive monitoring and other attacks, it is appropriate to require securing relay to relay and relay to server communication for DHCPv6 and relay to server communication for DHCPv4. The IETF datatracker status page for this draft is: https://datatracker.ietf.org/doc/draft-ietf-dhc-relay-server-security/ There's also a htmlized version available at: https://tools.ietf.org/html/draft-ietf-dhc-relay-server-security-03 A diff from the previous version is available at: https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-relay-server-security-03 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. Internet-Drafts are also available by anonymous FTP at: ftp://ftp.ietf.org/internet-drafts/
- [dhcwg] I-D Action: draft-ietf-dhc-relay-server-s… internet-drafts
- Re: [dhcwg] I-D Action: draft-ietf-dhc-relay-serv… Bernie Volz (volz)