Re: [OPSEC] [v6ops] Fwd: WGLC for draft-ietf-opsec-v6

Hi:

In 2.6.1.5.  Stateful DHCPv6 Lease:

   In short, the DHCPv6 lease file is less interesting than in the IPv4
   era.  DHCPv6 servers that keeps the relayed data-link layer address
   in addition to the DUID in the lease file do not suffer from this
   limitation.

You should add an informative reference to rfc6939, Client Link-Layer Address Option in DHCPv6. This is a way to obtain the data-link layer address of the client (at least in relayed environments). I'm not really sure how DHCPv6 servers could do this without this option as without it there is no way for the server to obtain the data-link layer address of the client otherwise.

Also, it should be "DHCPv6 servers that keep ..."?

-          Bernie

From: v6ops [mailto:v6ops-bounces@ietf.org] On Behalf Of Gunter Van De Velde
Sent: Tuesday, April 18, 2017 3:18 AM
To: 6man@ietf.org; v6ops@ietf.org
Subject: [v6ops] Fwd: [OPSEC] WGLC for draft-ietf-opsec-v6

Dear 6man, v6ops,

Due to the IPv6 focus of "draft-ietf-opsec-v6" the OPSEC WGLC for this document may be of interest to both 6man as v6ops.

Please send your feedback to OPSEC email list, where discussion around this document should take place.

Kind Regards,
G/

Begin forwarded message:

From: Gunter Van De Velde <guntervandeveldecc@icloud.com<mailto:guntervandeveldecc@icloud.com>>
Subject: [OPSEC] WGLC for draft-ietf-opsec-v6
Date: 12 April 2017 at 09:39:28 GMT+2
To: opsec@ietf.org<mailto:opsec@ietf.org>

This is to open a two week WGLC for https://tools.ietf.org/html/draft-ietf-opsec-v6.
If you have not read it, please do so now. You may send nits to the author, but substantive discussion should go to the list.

I will close the call on 26 April 2017

G/

Sent from iCloud
_______________________________________________
OPSEC mailing list
OPSEC@ietf.org<mailto:OPSEC@ietf.org>
https://www.ietf.org/mailman/listinfo/opsec