[dhcwg] Adam Roach's No Objection on draft-ietf-dhc-relay-port-07: (with COMMENT)

Adam Roach <adam@nostrum.com> Wed, 29 November 2017 01:30 UTC

Return-Path: <adam@nostrum.com>
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 B8CBB126DFE; Tue, 28 Nov 2017 17:30:32 -0800 (PST)
MIME-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: 7bit
From: Adam Roach <adam@nostrum.com>
To: The IESG <iesg@ietf.org>
Cc: draft-ietf-dhc-relay-port@ietf.org, Tomek Mrugalski <tomasz.mrugalski@gmail.com>, dhc-chairs@ietf.org, tomasz.mrugalski@gmail.com, dhcwg@ietf.org
X-Test-IDTracker: no
X-IETF-IDTracker: 6.66.0
Auto-Submitted: auto-generated
Precedence: bulk
Message-ID: <151191903274.8045.11660427093374661131.idtracker@ietfa.amsl.com>
Date: Tue, 28 Nov 2017 17:30:32 -0800
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/LWGhqt6osmpN_pISNhSkJEnXYr4>
Subject: [dhcwg] Adam Roach's No Objection on draft-ietf-dhc-relay-port-07: (with COMMENT)
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
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: Wed, 29 Nov 2017 01:30:33 -0000

Adam Roach has entered the following ballot position for
draft-ietf-dhc-relay-port-07: No Objection

When responding, please keep the subject line intact and reply to all
email addresses included in the To and CC lines. (Feel free to cut this
introductory paragraph, however.)


Please refer to https://www.ietf.org/iesg/statement/discuss-criteria.html
for more information about IESG DISCUSS and COMMENT positions.


The document, along with other ballot positions, can be found here:
https://datatracker.ietf.org/doc/draft-ietf-dhc-relay-port/



----------------------------------------------------------------------
COMMENT:
----------------------------------------------------------------------

Thanks for your time on this document. I have one minor correction and two
questions.

The introduction says: "...for IPv6 the server port is (546) and the client
port is (547)."  I believe this is backwards.

Section 5.2 says:

   If this option is included to
   indicate only the local non-DHCP UDP port usage and there is no
   downstream relay agent's non-DHCP UDP port usage, the field
   Downstream Source Port field MUST be set to zero.

Was the use of length=0 considered rather that port=0 here? The reason I ask is
that UDP port 0 is *reserved*, but not technically *invalid*, and the use of
"length=0" would distinguish between the flag usage and the port usage while
not precluding the valid (if admittedly rare) use of port=0.

Finally, I have a question about DHCPv6 relay agent chains that arose in
reading the document. The example section actually gives a pretty good jumping
off point to ask the question, so I'll quote an excerpt here:

   Similar to the above example, now assume that Relay2 uses the UDP
   source port of 2000 instead of 547 as in the diagram.  The Relay3
   device needs to support this DHCP extension and it will set 2000 in
   its "Downstream Source Port" field of the option in the Relay-forward
   message.  When DHCP server sends the DHCP Relay-reply to Relay3,
   Relay3 finds its own relay option has this "Downstream Source Port"
   with the value of 2000.  Relay3 will use this UDP port when sending
   the Relay-reply message to Relay2.

If we were to continue this paragraph all the way back to Relay1, it's not
clear how Relay2 would know to use port 1000 when sending its Relay-reply
message to Relay1. Does this mechanism have a limitation that only one Relay
Agent in the forwarding chain is allowed to use a Non-DHCP UDP Port?