Re: [dhcwg] I-D Action: draft-ietf-dhc-relay-server-security-01.txt

Hi Bernie,

Just so I can understand the intent of this document, if the relay(s) and server
already know that some form of encryption is already in use (e.g., if the client
and server are using sedhcpv6) then it should be OK to omit encryption between
the Relay and Server. Does this draft intend to mandate the use of encryption
in all cases?

Thanks - Fred

> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
> Sent: Monday, October 17, 2016 6:58 AM
> To: dhcwg@ietf.org
> Subject: Re: [dhcwg] I-D Action: draft-ietf-dhc-relay-server-security-01.txt
> 
> Hi:
> 
> This update was a very minor change suggested by Stephen Farrell. In section 3, the last sentence in the 1st paragraph was updated to
> add "and other attacks", since this not only protects against pervasive monitoring.
> 
> - Bernie
> 
> -----Original Message-----
> From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of internet-drafts@ietf.org
> Sent: Monday, October 17, 2016 9:54 AM
> To: i-d-announce@ietf.org
> Cc: dhcwg@ietf.org
> Subject: [dhcwg] I-D Action: draft-ietf-dhc-relay-server-security-01.txt
> 
> 
> 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-01.txt
> 	Pages           : 8
> 	Date            : 2016-10-17
> 
> 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 recommend
>    encryption.  And, with recent concerns about pervasive monitoring it
>    is appropriate to provide recommendations for DHCPv4 and also improve
>    the recommendations for DHCPv6.  This document updates RFC1542 and
>    RFC3315.
> 
> 
> 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-01
> 
> A diff from the previous version is available at:
> https://www.ietf.org/rfcdiff?url2=draft-ietf-dhc-relay-server-security-01
> 
> 
> 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 mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg