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:02 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 9918C129631 for <dhcwg@ietfa.amsl.com>; Thu, 6 Apr 2017 17:02:35 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -14.522
X-Spam-Level:
X-Spam-Status: No, score=-14.522 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, 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 mxKUd0KVl73r for <dhcwg@ietfa.amsl.com>; Thu, 6 Apr 2017 17:02:34 -0700 (PDT)
Received: from alln-iport-6.cisco.com (alln-iport-6.cisco.com [173.37.142.93]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id D62DF1292C5 for <dhcwg@ietf.org>; Thu, 6 Apr 2017 17:02:33 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1384; q=dns/txt; s=iport; t=1491523353; x=1492732953; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=NraipCh8fKHUGNzF88RZiqP5fAbtbupmRlIMUh3In9A=; b=ARaBd7GjIaOL2WEba36bEB2UwiBqnufSUsWN/T5qpT1SSCenF/Dm63Cz 542SS/qb3M3rQRVaggY7zSj9Z7pLSJXYk1dbwdLGXUGYc0opcIcn1vwK3 BT1paJYUOh7JEUek+MLPyMfsxSE9y1OX7/cLLFlv8grEaVVH5Zv+LRYGh A=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: =?us-ascii?q?A0AhAQCF1uZY/49dJa1cGQEBAQEBAQEBA?= =?us-ascii?q?QEBBwEBAQEBg1RhgQsHAY1tkUCVVYIPHwuFeAIagy4/GAECAQEBAQEBAWsohRU?= =?us-ascii?q?BAQEBAgEBASEROgsFCwIBCA4KAgImAgICJQsVEAIEDgWKBggOqTmCJopyAQEBA?= =?us-ascii?q?QEBAQEBAQEBAQEBAQEBAQEBGAWBC4dIgmuBPIMECYMTLoIxBZxzAZJSkT2TdwE?= =?us-ascii?q?fOIEFWxVBEQGEVoFzdYckgS4BgQwBAQE?=
X-IronPort-AV: E=Sophos;i="5.37,161,1488844800"; d="scan'208";a="408746355"
Received: from rcdn-core-7.cisco.com ([173.37.93.143]) by alln-iport-6.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 07 Apr 2017 00:02:33 +0000
Received: from XCH-RCD-005.cisco.com (xch-rcd-005.cisco.com [173.37.102.15]) by rcdn-core-7.cisco.com (8.14.5/8.14.5) with ESMTP id v3702WUO022733 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Fri, 7 Apr 2017 00:02:33 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:02:32 -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:02:32 -0500
From: "Naiming Shen (naiming)" <naiming@cisco.com>
To: Ted Lemon <mellon@fugue.com>
CC: Tomek Mrugalski <tomasz.mrugalski@gmail.com>, dhcwg <dhcwg@ietf.org>
Thread-Topic: [dhcwg] WGLC on draft-ietf-dhc-relay-port-02 - respond by Apr 26
Thread-Index: AQHSrkJ4H/Lr+ZM5zE2RbI5PHueQ0qG5TpaAgAANOAA=
Date: Fri, 7 Apr 2017 00:02:32 +0000
Message-ID: <BC8EABF0-A7EB-42EF-A78A-9B1DAC2A12C1@cisco.com>
References: <4cb9bdab-f3a2-a9d0-1056-302b5ecdeae7@gmail.com> <6815847B-EEB6-4824-959E-F8D845A14994@fugue.com>
In-Reply-To: <6815847B-EEB6-4824-959E-F8D845A14994@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: text/plain; charset="utf-8"
Content-ID: <0F75FD7A57840F419BF6B8B1F7EAFDC4@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <https://mailarchive.ietf.org/arch/msg/dhcwg/TolyfghBHGezTGvq7VeEmdj3Rw4>
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:02:36 -0000

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.




Best Regards,
- Naiming

> On Apr 6, 2017, at 4:15 PM, Ted Lemon <mellon@fugue.com> wrote:
> 
> I support advancing this work.   However, there is an issue: right now the document assumes that if the relay agent sends a message from a different source port, the DHCP server will reply to that port.   This should be stated explicitly.  Right now the document does not place requirements on DHCP servers as far as I can see, and those are needed for interoperability.
> 
> _______________________________________________
> dhcwg mailing list
> dhcwg@ietf.org
> https://www.ietf.org/mailman/listinfo/dhcwg