Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014

<ian.farrer@telekom.de> Mon, 27 October 2014 19:22 UTC

Return-Path: <ian.farrer@telekom.de>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id D41B21AD062 for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 12:22:54 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -3.859
X-Spam-Level:
X-Spam-Status: No, score=-3.859 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_EQ_DE=0.35, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 VFa9GICQKlkU for <dhcwg@ietfa.amsl.com>; Mon, 27 Oct 2014 12:22:42 -0700 (PDT)
Received: from tcmail13.telekom.de (tcmail13.telekom.de [80.149.113.165]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 459011AD045 for <dhcwg@ietf.org>; Mon, 27 Oct 2014 12:22:03 -0700 (PDT)
Received: from q4de8psa169.blf.telekom.de ([10.151.13.200]) by tcmail11.telekom.de with ESMTP; 27 Oct 2014 20:22:00 +0100
X-IronPort-AV: E=Sophos;i="5.04,797,1406584800"; d="scan'208,217";a="688651428"
Received: from he111629.emea1.cds.t-internal.com ([10.134.93.21]) by q4de8psazkj.blf.telekom.de with ESMTP/TLS/AES128-SHA; 27 Oct 2014 20:22:00 +0100
Received: from HE111643.EMEA1.CDS.T-INTERNAL.COM ([10.134.93.12]) by HE111629.emea1.cds.t-internal.com ([::1]) with mapi; Mon, 27 Oct 2014 20:22:00 +0100
From: <ian.farrer@telekom.de>
To: <volz@cisco.com>, <dhcwg@ietf.org>
Date: Mon, 27 Oct 2014 20:21:58 +0100
Thread-Topic: WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
Thread-Index: Ac/minMIxUbYwkSiQNCrNLgZzh2MnQLAB7KgACCNBVA=
Message-ID: <8A1B81989BCFAE44A22B2B86BF2B76318B33AEA6C9@HE111643.EMEA1.CDS.T-INTERNAL.COM>
References: <489D13FBFA9B3E41812EA89F188F018E1B6C78C7@xmb-rcd-x04.cisco.com> <489D13FBFA9B3E41812EA89F188F018E1B6F6B1D@xmb-rcd-x04.cisco.com>
In-Reply-To: <489D13FBFA9B3E41812EA89F188F018E1B6F6B1D@xmb-rcd-x04.cisco.com>
Accept-Language: en-US, de-DE
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
acceptlanguage: en-US, de-DE
Content-Type: multipart/alternative; boundary="_000_8A1B81989BCFAE44A22B2B86BF2B76318B33AEA6C9HE111643EMEA1_"
MIME-Version: 1.0
Archived-At: http://mailarchive.ietf.org/arch/msg/dhcwg/-fkQqbFS0xjzGbeG0VRqVzQgZ1Q
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.15
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: <http://www.ietf.org/mail-archive/web/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, 27 Oct 2014 19:22:55 -0000

Hi Bernie,

Many thanks for the review. Please see inline.

Cheers,
Ian

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Montag, 27. Oktober 2014 04:08
To: dhcwg@ietf.org
Subject: Re: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014

While I am ok advancing this work if someone feels they need it (I would prefer we not deploy this technology and just move to IPv6 - especially as this requires making changes to hosts), I do have review comments that I believe need to be addressed:

In 1. Introduction, why reference ietf-dhc-dhcpv4-over-ip6v4? That work was an alternative to what became RFC 7341 and the WG decided that dhpv4-over-dhcpv6 was the way forward. Perhaps just drop "such as DHCPv4 over IPv6 [reference]"?

[if] I'm happy to remove this. IIRC, the ref was left in there when DHCPv4oIPv6 was intended to be an experimental RFC, but as it's no longer being updated, then it can go.

In the next paragraph, RFC 6346 is mentioned - this is an Experimental document. It is only an informational reference, so at least that may be OK. But it seems a bit odd that the text here is "This extension is only suitable for specific architectures based on Address plus Port model" when that is experimental? Even draft-ietf-softwire-map-t (-06) is going for Experimental, not standards track. (Though draft-ietf-softwire-map is going for Standards Track.)

[if] How about updating that sentence to read:
This extension is only suitable for specific architectures based on the Address plus Port model (A+P) [RFC6346], such as [I-D.ietf-softwire-lw4o6] and [I-D.ieft-softwire-map].

In 4. Functional Overview:

-          In the 2nd paragraph, this option is only used in the PRL in the DHCPDISCOVER? It is send by the client in DHCPREQUEST (DHCPRELEASE) messages. Perhaps this should be indicated?
[if] Propose the sentence with the wording
The client includes this option within the Parameter Request List option [RFC2132] in its DHCPv4 request, indicating its support for shared, dynamic address leasing to the DHCP 4o6 server.
Is updated to:
The client includes this option within the Parameter Request List option [RFC2132] in DHCPv4 DHCPDISCOVER and DHCPREQUEST messages, indicating its support for shared, dynamic address leasing to the DHCP 4o6 server.

>From my reading of RFC2131 (sec 4.4.1), PRL is not included in the DHCPRELEASE message.


-          I think in the last paragraph, first sentence, which should be that? ... to identify clients that support?

[if] New wording proposal:
OPTION_V4_PORTPARAMS is also implemented by the server so that clients supporting shared, dynamic address leasing can be
identified and so that shared IPv4 address and PSID leases can be  allocated and maintained.

In 5. Client-Server Interactions:

-          In #1, there is an opened parenthesis that is never closed.

[if] Will fix.


-          In #3, what if the client receives offers without the OPTION_V4_PORTPARAMS? Should it prefer that (I would think so)? (You do mention this later in section 7.)

[if] OK, I'll add some text to prefer the full address.


-          Ted already pointed out the issue in the last paragraph with RFC 2131 3.2 and that a DHCPREQUEST is sent, not a DHCPDISCOVER. I think this will also need some careful attention as this could result in problems if the client ends up on a different network and a server decides to allocate the requested address but doesn't support OPTION_V4_PORTPARAMs? First, I think perhaps using input from the IPv6 layer (i.e., as this is using RFC7341) can help since if the V6 stack determines the location has changed, then obviously going to DHCPDISCOVER is the better choice? (Not sure if perhaps we should recommend that existing "traditional" DHCP servers that receive a DHCPREQUEST (init-reboot) with an OPTION_V4_PORTPARAMS should either drop the packet or send a DHCPNAK it?

[if] I can add some text into the client behavior section saying:
"In the event that the client's DHCPv4o6 IPv6 source address is  changed for any reason, the client MUST re-initiate the DHCPv4o6 shared-address provisioning process by sending a DHCPDISCOVER message".

For recommending that 'traditional' DHCP servers, can we meaningfully do that in this spec? Surely existing server implementations will behave as they do, unless this is positioned as an update to RFC7341?
In 6. Server Behavior, un the 2nd paragraph "server MUST run an address and port-set" is rather odd wording? Do you implemented instead of run?

[if] Agreed. Will change.

Section 7. Client Behavior is rather similar to section 5. Kind of a bit odd order (perhaps Client-Server Interactions, Client Behavior, Server Behavior would be a bit better, but not a big deal).

[if] OK. I'll reorder them.

In 7.1, is there any RFC to reference here that describes the limitations for a node with a limited port set? For the first bulleted item, do we know what "port-aware" protocols are? I think this is not a common term, so it will have to be defined? Also for the sentence that introduces the list "Client MUST apply ... to ... the shared address"? I think what you mean here is if it provides information to another node to make connections back (into) the client, it must use its port range?

[if] We could reword to: Only port-aware protocols (e.g TCP, UDP, DCCP etc.) or ICMP implementing [RFC5508] MUST be used.
For the second point, the intention is to restrict outgoing connection's source port and service listeners to being initiated only with protocols that have L4 ports, and only to use the specific range of ports which have been provisioned to it. Can this be clarified by changing the intro sentence to?:

The client MUST apply the following rules for all traffic destined to or originating from the shared IPv4 address

In 9.1, isn't there also a problem if a malicious client doesn't follow the rules in section 7.1 if there isn't proper filtering in place (i.e., egress filtering).

[if] For this to be a problem, there would need to be operator mis-configuration in the A+P border router, and matching malicious configuration on the client. As lw4o6 & MAP implement ingress and egress checks that the packets received are valid (i.e. there must be a match between the v6 address, and source IPv4 address and L4 ports for decap and a valid IPv4 address and dst port for encap).  As this is data-plane functionality, and this draft is concerned with provisioning, do you think this needs to be re-iterated here?


-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Bernie Volz (volz)
Sent: Sunday, October 12, 2014 10:14 PM
To: dhcwg@ietf.org<mailto:dhcwg@ietf.org>
Subject: [dhcwg] WGLC for draft-ietf-dhc-dynamic-shared-v4allocation-02 - Respond by Oct 27, 2014


Hi all,



This message starts the DHC working group last call to advance "Dynamic Allocation of Shared IPv4 Addresses", draft-ietf-dhc-dynamic-shared-v4allocation-02, document as a Standards Track (Proposed Standard) RFC. The authors believe that this version is ready.



The draft is available here:

http://tools.ietf.org/html/draft-ietf-dhc-dynamic-shared-v4allocation-02



Please send your comments by October 27th, 2014. If you do not feel this document should advance, please state your reasons why.



There are no IPR claims reported at this time.



Bernie Volz is the currently assigned shepherd for this document.



- Tomek & Bernie