Newsgroups: php.internals Path: news.php.net Xref: news.php.net php.internals:99510 Return-Path: Mailing-List: contact internals-help@lists.php.net; run by ezmlm Delivered-To: mailing list internals@lists.php.net Received: (qmail 99087 invoked from network); 13 Jun 2017 15:03:34 -0000 Received: from unknown (HELO lists.php.net) (127.0.0.1) by localhost with SMTP; 13 Jun 2017 15:03:34 -0000 Authentication-Results: pb1.pair.com smtp.mail=newaltgroup@bk.ru; spf=pass; sender-id=pass Authentication-Results: pb1.pair.com header.from=newaltgroup@bk.ru; sender-id=pass Received-SPF: pass (pb1.pair.com: domain bk.ru designates 94.100.177.96 as permitted sender) X-PHP-List-Original-Sender: newaltgroup@bk.ru X-Host-Fingerprint: 94.100.177.96 smtp36.i.mail.ru Received: from [94.100.177.96] ([94.100.177.96:49042] helo=smtp36.i.mail.ru) by pb1.pair.com (ecelerity 2.1.1.9-wez r(12769M)) with ESMTP id 88/C8-00089-2CEFF395 for ; Tue, 13 Jun 2017 11:03:32 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=bk.ru; s=mail; h=Mime-Version:To:Date:Message-Id:Subject:Content-Transfer-Encoding:Content-Type:From; bh=TCcCF5Rc/6V5z2acgNLtJHFI4Om4i6mAwGM8Y/19Ly4=; b=NLWU98XQHpw1r355gbRQwxab+X6QjMTDKxQ4tgjbcdLTO56xtA3GtjFos3Fpv+DoawVQiN5hoXtzusLmJOqccxuQg34KvyTEtqn7Wdp8qxztFT/WfrOsuJxxoIoK/Q9Qi35g1fUOv3mhbKV5TQC491SMswNHd4raW072wiQx/Ko=; Received: from mm-21-81-44-37.mgts.dynamic.pppoe.byfly.by ([37.44.81.21]:3219 helo=[192.168.100.22]) by smtp36.i.mail.ru with esmtpa (envelope-from ) id 1dKnLr-00033v-Eg for internals@lists.php.net; Tue, 13 Jun 2017 18:03:27 +0300 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Message-ID: <6DB2D22F-A500-4D3B-83DD-EC0CD0396801@bk.ru> Date: Tue, 13 Jun 2017 18:03:25 +0300 To: internals@lists.php.net Mime-Version: 1.0 (Mac OS X Mail 9.3 \(3124\)) X-Mailer: Apple Mail (2.3124) Authentication-Results: smtp36.i.mail.ru; auth=pass smtp.auth=newaltgroup@bk.ru smtp.mailfrom=newaltgroup@bk.ru X-7FA49CB5: 0D63561A33F958A58E1B3BBBBDF9506D6A57F7E4FC05383DDB1A8CF8E19B02E9725E5C173C3A84C376F138C68E4EE6C9E85C60F133C97C27444A83B712AC0148C4224003CC836476C0CAF46E325F83A50BF2EBBBDD9D6B0F05F538519369F3743B503F486389A921A5CC5B56E945C8DA X-Mailru-Sender: 3155A1A230043989263DD183C5A046123212AF2744BF5FEFA2286294E035510EE00FC740349CC523D617EA2584B8689CFB559BB5D741EB9633696525C9D1D49EC42AFB4B603C56BB0DA7A0AF5A3A8387 X-Mras: OK Subject: [Bug] [Discussion] filter_var and reserved IP address range From: newaltgroup@bk.ru (Andrew Nester) Hello! Currently I am working on bug #74699 (Thanks brianlmoon for pointing = this issue). Here is some details: In patch applied for bug #72972 IP address block 240.0.0.0/4 has been = removed from list of reserved. But according to IP Multicast Address Specification: =E2=80=9CThe range of addresses between 224.0.0.0 and 224.0.0.255, = inclusive, is reserved for the use of routing protocols and other low-leveltopology = discovery or maintenance protocols,=20 such as gateway discoveryand group membership reporting. =20 Multicast routers should not forwardany multicast datagram with = destination addresses in this range,regardless of its TTL.=E2=80=9D Here is the full specification:=20 = https://www.iana.org/assignments/multicast-addresses/multicast-addresses.x= html That=E2=80=99s why my PR introducing changes to include addresses = between 224.0.0.0 and 224.0.0.255 in list of reserved. Here is link to my PR https://github.com/php/php-src/pull/2562 Thanks!=