Re: [dhcwg] I-D Action: draft-shen-dhc-client-port-01.txt

"Bernie Volz (volz)" <volz@cisco.com> Fri, 08 July 2016 19:04 UTC

Return-Path: <volz@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 1F05F12D828 for <dhcwg@ietfa.amsl.com>; Fri, 8 Jul 2016 12:04:21 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.946
X-Spam-Level:
X-Spam-Status: No, score=-15.946 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_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_PASS=-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 ytW7C2wWpjmc for <dhcwg@ietfa.amsl.com>; Fri, 8 Jul 2016 12:04:18 -0700 (PDT)
Received: from alln-iport-1.cisco.com (alln-iport-1.cisco.com [173.37.142.88]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 8DA8912D686 for <dhcwg@ietf.org>; Fri, 8 Jul 2016 12:04:16 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=26974; q=dns/txt; s=iport; t=1468004656; x=1469214256; h=from:to:subject:date:message-id:references:in-reply-to: mime-version; bh=69ZWCr1UO1RlX70jAoZX/cRJ4FQSx/yeaS+8MPm/IPQ=; b=N5fa8IVvjCHUUzSRtwZ8Tkp3/EM+w81i8OfAP9iGbnaaDtFqI9oD5cew ktExL+30Gh4pemDPaBSpA7zwRfmJSVDWa4aMOY+vB0fV9JTH46DOgcXil 60l3Yu5ad6YEFVW8Y0sNpr1H9yvEiKNCl2mZTGRrzwVeND1KCHFJEkkbz I=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0D/AQDG+H9X/40NJK1cgnBOVnwGuQyBe?= =?us-ascii?q?yKFdgIcgQw4FAEBAQEBAQFlJ4RMAQEFAQEhCkEbAgEIEQMBAQEhBwMCAgIlCxQ?= =?us-ascii?q?JCAIEARIIAYgnDq52jykBAQEBAQEBAQEBAQEBAQEBAQEBAQEcinSEKy0JFoITO?= =?us-ascii?q?IJaBZNahToBhguIPIFxToQKh0+BG4gxh1wBHjaDcW4BiDJ/AQEB?=
X-IronPort-AV: E=Sophos;i="5.28,331,1464652800"; d="scan'208,217";a="295518852"
Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-1.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 08 Jul 2016 19:04:15 +0000
Received: from XCH-RCD-001.cisco.com (xch-rcd-001.cisco.com [173.37.102.11]) by alln-core-8.cisco.com (8.14.5/8.14.5) with ESMTP id u68J4FG1031265 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for <dhcwg@ietf.org>; Fri, 8 Jul 2016 19:04:15 GMT
Received: from xch-aln-003.cisco.com (173.36.7.13) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1210.3; Fri, 8 Jul 2016 14:04:14 -0500
Received: from xch-aln-003.cisco.com ([173.36.7.13]) by XCH-ALN-003.cisco.com ([173.36.7.13]) with mapi id 15.00.1210.000; Fri, 8 Jul 2016 14:04:14 -0500
From: "Bernie Volz (volz)" <volz@cisco.com>
To: "Naiming Shen (naiming)" <naiming@cisco.com>, "dhcwg@ietf.org" <dhcwg@ietf.org>
Thread-Topic: I-D Action: draft-shen-dhc-client-port-01.txt
Thread-Index: AQHR2M8PtDgyaoUgHE2ggSXIc0+FlqAO5D0Q
Date: Fri, 8 Jul 2016 19:04:14 +0000
Message-ID: <adb4507f1c9947478d3e613271a98367@XCH-ALN-003.cisco.com>
References: <20160708041305.18785.16916.idtracker@ietfa.amsl.com> <FDE950BA-7E7F-4D7E-912C-C324B628A246@cisco.com>
In-Reply-To: <FDE950BA-7E7F-4D7E-912C-C324B628A246@cisco.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.98.1.197]
Content-Type: multipart/alternative; boundary="_000_adb4507f1c9947478d3e613271a98367XCHALN003ciscocom_"
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/xHHBjjZ3PmlFwHnT3ApWsZoQFdY>
Subject: Re: [dhcwg] I-D Action: draft-shen-dhc-client-port-01.txt
X-BeenThere: dhcwg@ietf.org
X-Mailman-Version: 2.1.17
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, 08 Jul 2016 19:04:21 -0000

Hi:

Some initial comments:


1.       For DHCPv4, the zero length option can work since there is no provision for relay chaining.

2.       For DHCPv6, the zero length option does NOT work since this provides no means for a case where Relay 1 uses port X which is sent to Relay 2 which uses port Y to send to the Server. The server can response to Relay 2 on port Y (since that is the incoming port), but there is no place for Relay 2 to have stored the port. You should go back and make this option a 2 octet option with the port number. The server would then see:

Relay-Forw from Relay 2

                Relay Port Source Port option Y

                Relay-Message option

                                Relay-Forw from Relay 1

                                                Relay Port source Port option X

                                                Relay- Message Option

                                                                <client’s request>
                And all would work correctly as the Server would use the port Y from the outermost relay option, relay 2 would use the port X from the Relay 1 Relay-Forw.



-          Bernie

From: dhcwg [mailto:dhcwg-bounces@ietf.org] On Behalf Of Naiming Shen (naiming)
Sent: Friday, July 08, 2016 12:29 AM
To: dhcwg@ietf.org
Subject: [dhcwg] Fwd: I-D Action: draft-shen-dhc-client-port-01.txt


Hi,

We have updated the draft of “Generalized Source UDP Port of DHCP Relay”.
Please review and comment.

Thanks.
- Naiming


Begin forwarded message:

From: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>
Subject: I-D Action: draft-shen-dhc-client-port-01.txt
Date: July 7, 2016 at 9:13:05 PM PDT
To: <i-d-announce@ietf.org<mailto:i-d-announce@ietf.org>>
Reply-To: internet-drafts@ietf.org<mailto:internet-drafts@ietf.org>


A New Internet-Draft is available from the on-line Internet-Drafts directories.


       Title           : Generalized Source UDP Port of DHCP Relay
       Authors         : Naiming Shen
                         Enke Chen
Filename        : draft-shen-dhc-client-port-01.txt
Pages           : 7
Date            : 2016-07-07

Abstract:
  This document extends the DHCP and DHCPv6 protocols for the UDP
  transport from relay agent to server and allows the port to be any
  valid number on the DHCP relay system.


The IETF datatracker status page for this draft is:
https://datatracker.ietf.org/doc/draft-shen-dhc-client-port/

There's also a htmlized version available at:
https://tools.ietf.org/html/draft-shen-dhc-client-port-01

A diff from the previous version is available at:
https://www.ietf.org/rfcdiff?url2=draft-shen-dhc-client-port-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/

_______________________________________________
I-D-Announce mailing list
I-D-Announce@ietf.org
https://www.ietf.org/mailman/listinfo/i-d-announce
Internet-Draft directories: http://www.ietf.org/shadow.html
or ftp://ftp.ietf.org/ietf/1shadow-sites.txt