Re: [dhcwg] WGLC on draft-ietf-dhc-relay-port-02 - respond by Apr 26

"Naiming Shen (naiming)" <naiming@cisco.com> Fri, 07 April 2017 00:26 UTC

Return-Path: <naiming@cisco.com>
X-Original-To: dhcwg@ietfa.amsl.com
Delivered-To: dhcwg@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E38881286CA for <dhcwg@ietfa.amsl.com>; Thu, 6 Apr 2017 17:26:45 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.521
X-Spam-Level:
X-Spam-Status: No, score=-14.521 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.001, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (1024-bit key) header.d=cisco.com
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 LVbbcSiN4gty for <dhcwg@ietfa.amsl.com>; Thu, 6 Apr 2017 17:26:43 -0700 (PDT)
Received: from alln-iport-5.cisco.com (alln-iport-5.cisco.com [173.37.142.92]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 98205127275 for <dhcwg@ietf.org>; Thu, 6 Apr 2017 17:26:42 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=11268; q=dns/txt; s=iport; t=1491524802; x=1492734402; h=from:to:cc:subject:date:message-id:references: in-reply-to:mime-version; bh=J34VoMd5QdlzeQxRjeEx5pNFLOLmJMvYh/gKNK3wsO8=; b=J/yjRzCh8vIZ8iayHNH7WoPzba9wK6IJUSxqCpw802TBpoGzCkM0mHqJ 6D7OdB6Sm8ODIlvaGl/pa3CS3ADXB4ZlHWICbJMC4bdvqQ7DVsOuqms7X 9PZkiVFyyKKH4KK//8orkaYGjcvPuXjKdWh+FH7AALXTfXcPz25iA4lr9 c=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0CdAQCp2+ZY/4MNJK1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1RhgQsHAY1tkSGQQIU0gg8mhXwCGoMuPxgBAgEBAQEBAQFrKIU?= =?us-ascii?q?WBiNWEAIBCA4xAwICAjAUEQIEDgWKDg6pP4IminMBAQEBAQEBAQEBAQEBAQEBA?= =?us-ascii?q?QEBAQEYBYhTCYJigTyDBAmDEy6CMQWccwGGfYtVgX6JB4Y4k3cBHziBBVsVUgG?= =?us-ascii?q?EVoFzdYckgS4BgQwBAQE?=
X-IronPort-AV: E=Sophos;i="5.37,161,1488844800"; d="scan'208,217";a="406940038"
Received: from alln-core-1.cisco.com ([173.36.13.131]) by alln-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 07 Apr 2017 00:26:41 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by alln-core-1.cisco.com (8.14.5/8.14.5) with ESMTP id v370Qf1P027965 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 00:26:41 GMT
Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-RCD-005.cisco.com (173.37.102.15) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Thu, 6 Apr 2017 19:26:40 -0500
Received: from xch-rcd-004.cisco.com ([173.37.102.14]) by XCH-RCD-004.cisco.com ([173.37.102.14]) with mapi id 15.00.1210.000; Thu, 6 Apr 2017 19:26:40 -0500
From: "Naiming Shen (naiming)" <naiming@cisco.com>
To: Ted Lemon <mellon@fugue.com>
CC: dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC on draft-ietf-dhc-relay-port-02 - respond by Apr 26
Thread-Index: AQHSrkJ4H/Lr+ZM5zE2RbI5PHueQ0qG5TpaAgAANOACAAABMAIAAA0oAgAAAoACAAAKIAA==
Date: Fri, 7 Apr 2017 00:26:40 +0000
Message-ID: <2AD20D47-6D22-404E-9796-662C7CBB4630@cisco.com>
References: <4cb9bdab-f3a2-a9d0-1056-302b5ecdeae7@gmail.com> <6815847B-EEB6-4824-959E-F8D845A14994@fugue.com> <BC8EABF0-A7EB-42EF-A78A-9B1DAC2A12C1@cisco.com> <51E35331-9AFA-4C75-851D-129AF3E3F5A8@fugue.com> <DF64443D-4C36-4285-83EF-32FA32372B87@cisco.com> <FEC317CE-2499-402E-92DF-C9349B9560B2@fugue.com>
In-Reply-To: <FEC317CE-2499-402E-92DF-C9349B9560B2@fugue.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [128.107.155.135]
Content-Type: multipart/alternative; boundary="_000_2AD20D476D22404E9796662C7CBB4630ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/bSM9xZCJRb8wQcCJHJsXoGXZcNw>
Subject: Re: [dhcwg] WGLC on draft-ietf-dhc-relay-port-02 - respond by Apr 26
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.22
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: <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: Fri, 07 Apr 2017 00:26:46 -0000

Ok, currently the text is this:

   The Relay Agent "Source Port Sub-option" is a new option, and it is
   part of the relay-agent-information option for DHCPv4 [RFC3046<https://tools.ietf.org/html/rfc3046>]6>].  It
   SHOULD be used by a relay agent that uses a non-DHCP UDP port
   communicating with the DHCP server.

I can change it to:


   The Relay Agent "Source Port Sub-option" is a new option, and it is
   part of the relay-agent-information option for DHCPv4 [RFC3046<https://tools.ietf.org/html/rfc3046>]6>].  It
   MUST be used by a relay agent that uses a non-DHCP UDP port
   communicating with the DHCP server.


and do the same for DHCPv6 part also.

Best Regards,
- Naiming

On Apr 6, 2017, at 5:17 PM, Ted Lemon <mellon@fugue.com<mailto:mellon@fugue.com>> wrote:

Hm, okay, but earlier you also specify that the router can just use a different source port without using the option.   If this isn't permitted, then you need to make that text more explicit: if and only if the relay sends the suboption can it use a different source port.

On Apr 6, 2017, at 5:15 PM, Naiming Shen (naiming) <naiming@cisco.com<mailto:naiming@cisco.com>> wrote:


Hi Ted,

In section 4.1 “Source Port Sub-option for DHCPv4", it says:

 When a DHCP server receives a message from a relay agent with the
 "Source Port Sub-option", it MUST remember the UDP source port of the
 message and use that port number as the UDP destination port when
 sending the reply message to the same relay agent.

In section 4.2 “Source Port Sub-option for DHCPv6", it says:

 When a DHCPv6 server receives a Relay-forward message with the "Relay
 Source Port Option", it MUST copy the option when constructing the
 Relay-reply chain in response to the Relay-forward message.  This
 option MUST NOT appear in any message other than a Relay-forward or
 Relay-reply message.  Additionally, the DHCPv6 server MUST check and
 use the UDP source port from the UDP packet of the Relay-forward
 message in replying to the relay agent.

thus the dhcp server behavior for both v4 and v6 is defined.

Best Regards,
- Naiming

On Apr 6, 2017, at 5:03 PM, Ted Lemon <mellon@fugue.com<mailto:mellon@fugue.com>> wrote:

No, that's not quite what I mean.   What I mean is that you have to explicitly say what the DHCP server does.   Right now I'm not seeing that.    Maybe I missed it—I read the document pretty quickly.

On Apr 6, 2017, at 5:02 PM, Naiming Shen (naiming) <naiming@cisco.com<mailto:naiming@cisco.com>> wrote:


Hi Ted,

Thanks for the suggestion. Currently in section 6 “Compatibility”, it says:

 It is recommended to upgrade the server side first before using a non-DHCP
 UDP port for a relay agent.

How about changing to this:

The DHCP server MUST be upgraded to support the extension specified
in this document before the extension is used by a relay agent.