Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-5.0 required=5.0 tests=RCVD_IN_DNSWL_HI, RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL,RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Ironport-Anti-Spam-Filtered: true Thread-Index: AQHTg8Gl0kv6I/oMJEK15Futj4VlRKNhWWqA In-Reply-To: To: "dhcp-public@isc.org" From: "Naiming Shen (naiming)" From naiming@cisco.com Tue Jan 2 19:16:44 2018 Return-Path: Received: from mx.pao1.isc.org (mx.pao1.isc.org [IPv6:2001:4f8:0:2::2b]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "mx.pao1.isc.org", Issuer "COMODO RSA Organization Validation Secure Server CA" (not verified)) by bugs.isc.org (Postfix) with ESMTPS id 45F12D78B0B for ; Tue, 2 Jan 2018 19:16:44 +0000 (UTC) Received: from alln-iport-8.cisco.com (alln-iport-8.cisco.com [173.37.142.95]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx.pao1.isc.org (Postfix) with ESMTPS id D3CDA3B6386 for ; Tue, 2 Jan 2018 19:16:41 +0000 (UTC) Received: from alln-core-8.cisco.com ([173.36.13.141]) by alln-iport-8.cisco.com with ESMTP/TLS/DHE-RSA-AES256-GCM-SHA384; 02 Jan 2018 19:16:23 +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 w02JGNfh023709 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL) for ; Tue, 2 Jan 2018 19:16:23 GMT Received: from xch-rcd-004.cisco.com (173.37.102.14) by XCH-RCD-001.cisco.com (173.37.102.11) with Microsoft SMTP Server (TLS) id 15.0.1320.4; Tue, 2 Jan 2018 13:16:22 -0600 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.1320.000; Tue, 2 Jan 2018 13:16:22 -0600 X-MS-Exchange-Messagesentrepresentingtype: 1 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on mx.pao1.isc.org X-Ironport-Av: E=Sophos;i="5.45,498,1508803200"; d="scan'208";a="50918729" Delivered-To: dhcp-public@bugs.isc.org CC: "Enke Chen (enkechen)" Message-ID: Content-ID: <54CE44B358F9F146ADF41E836B138741@emea.cisco.com> References: Date: Tue, 2 Jan 2018 19:16:22 +0000 X-MS-Exchange-Transport-Fromentityheader: Hosted Dkim-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1617; q=dns/txt; s=iport; t=1514920601; x=1516130201; h=from:to:cc:subject:date:message-id:references: in-reply-to:content-id:content-transfer-encoding: mime-version; bh=gWBGPKsnN6lAheOPySnOxWJx3i+lm7jbJ2cvFaqFGWY=; b=GksoVWEe9raocRs+hRYPE2yX1jD+pHXMuwDpXTVETGu3Q+PVEkoULX+K VTtC+krP/bp/Z2CvnWqNgbGdIoGm39aTFyd9ohcVHWFRDTRXrkfpsjYwY fNrJa0I4FLkymTN1d3sJ7e0btJa4bEMTGYz/ueW5FefrbC3YXjw6mvX7P 0=; X-RT-Interface: Email X-Originating-Ip: [10.24.85.188] X-RT-Incoming-Encryption: Not encrypted Subject: Re: [ISC-Bugs #44535] Patch: DHCP relay port feature code for review (from Cisco - Support ticket #11062) X-MS-Has-Attach: content-type: text/plain; charset="utf-8" Accept-Language: en-US X-RT-Original-Encoding: utf-8 MIME-Version: 1.0 Content-Language: en-US X-Original-To: dhcp-public@bugs.isc.org Thread-Topic: [ISC-Bugs #44535] Patch: DHCP relay port feature code for review (from Cisco - Support ticket #11062) X-MS-Tnef-Correlator: X-Ironport-Anti-Spam-Result: A0AkAQAW2kta/40NJK1dGQEBAQEBAQEBAQEBAQcBAQEBAYM+ZnQnB44kjxqCAZcqghUCCCOFGAKEMD8YAQEBAQEBAQEBax0LhSMBAQEBAgE6PwULAgEIGB4FCzIlAgQOBYomCBCxCgWDW4o5AQEBAQEBAQEBAQEBAQEBAQEBAQEBGAU0g1iCEoM/KYMFgUkBgWaBXhCDSII0BYpPmH0ClTOCF4YWi1ATlkMCERkBgTsBHzmBT28VZwGBfoJgKYFOeIZIK4EJgRYBAQE RT-Message-ID: Content-Length: 1517 Thanks Tomek for getting the earlier reservation of the codes. Happy New Year! Cheers, - Naiming > On Jan 2, 2018, at 4:02 AM, Tomasz Mrugalski via RT wrote: > > Hi, > > The draft (draft-ietf-dhc-relay-port) is now approved by IESG and is awaiting publication. It's a slow time because of Christmas and New Year, so the code allocation takes longer than usual. To make sure IANA assigned the codes, I asked them to assign option codes early. If you look at IANA page, these are marked as temporary, but don't worry. They'll become permanent once the RFC is published. Here's what I got: > > Tomek, all, > > These early allocations are complete. We've registered the following: > > 19 DHCPv4 Relay Source Port Sub-Option (TEMPORARY - registered 2017-12-27, expires 2018-12-27) [draft-ietf-dhc-relay-port] > > Please see > https://www.iana.org/assignments/bootp-dhcp-parameters > > 135 DHCPv6 Relay Source Port (TEMPORARY - registered 2017-12-27, expires 2018-12-27) [draft-ietf-dhc-relay-port] > > Please see > https://www.iana.org/assignments/dhcpv6-parameters > > If the document hasn't been approved for publication by then, we'll contact you in December 2018 to ask whether you want to renew for another year. Any renewals after the first one would require IESG approval. > > Best regards, > > Sabrina Tanamal > Senior IANA Services Specialist > > ----------- > > Please use those option codes when merging this patch. > > Tomek Mrugalski > (with my DHC co-chair hat on)