New issue
Advanced search Search tips

Issue 873490 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Aug 15
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

RFC 7526 Deprecated 6to4 Relay Anycast network in 2015

Reported by bkhow...@gmail.com, Aug 12

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/68.0.3440.106 Safari/537.36

Steps to reproduce the problem:
1. Look at current iana registry
2. Double check kReservedIPv4Ranges in IP_ADDRESS.CC
3. IANA deprecated 192.88.99.0/24 effective 2015-03

What is the expected behavior?
192.88.99.0/24 should not be marked reserved

What went wrong?
192.88.99.0/24 is marked reserved, per RFC 7526 the reservation for this network was deprecated.

https://tools.ietf.org/html/rfc7526

Did this work before? N/A 

Chrome version: 68.0.3440.106  Channel: stable
OS Version: 6.3
Flash Version: 

net\base\ip_address.cc should be amended, i.e.:

  } static const kReservedIPv4Ranges[] = {
      {{0, 0, 0, 0}, 8},     {{10, 0, 0, 0}, 8},      {{100, 64, 0, 0}, 10},
      {{127, 0, 0, 0}, 8},   {{169, 254, 0, 0}, 16},  {{172, 16, 0, 0}, 12},
-      {{192, 0, 2, 0}, 24},  {{192, 88, 99, 0}, 24},  {{192, 168, 0, 0}, 16},
-      {{198, 18, 0, 0}, 15}, {{198, 51, 100, 0}, 24}, {{203, 0, 113, 0}, 24},
-      {{224, 0, 0, 0}, 3}};
+      {{192, 0, 2, 0}, 24},    {{192, 168, 0, 0}, 16},  {{198, 18, 0, 0}, 15}, 
+      {{198, 51, 100, 0}, 24}, {{203, 0, 113, 0}, 24}, {{224, 0, 0, 0}, 3}};
 
Labels: Needs-Triage-M68
Components: Blink>Network
Labels: Triaged-ET TE-NeedsTriageHelp
The issue seems to be out of TE-scope as it is related to RFC 7526. Hence, adding label  TE-NeedsTriageHelp for further investigation from dev team.

Thanks...!!
Components: -Blink>Network Internals>Network
Labels: -OS-Windows
Section 4 of RFC 7526 deprecates the reservation of 192.88.99.0/24, and the deprecation is also listed on https://www.iana.org/assignments/iana-ipv4-special-registry/iana-ipv4-special-registry.xhtml. However, RFC 7526 states that "192.88.99.0/24 MUST NOT be reassigned for other use except by a future IETF Standards Action."

It appears to me these IP addresses have not been reassigned to any other protocols or allocated to an RIR. Given that this list is used for the function IPAddress::IsPubliclyRoutable, I'd say that they should stay in kReservedIPv4Ranges since IPv4 addresses in 192.88.99.0/24 are not publicly routable.

Is including this range of IP addresses in this list of ranges causing some sort of problem?
Labels: Needs-Feedback
I concur and this can be closed, thanks.

I was reviewing the new Chrome policy MediaRouterCastAllowAllIPs, which states "not just RFC1918/RFC4913 addresses" (should be RFC4193).  I wanted to verify that the other special use addresses were included, but also being cognizant of the issues with 1.1.1.1 was checking to make sure any things no longer reserved aren't hard coded.

https://www.chromium.org/administrators/policy-list-3#MediaRouterCastAllowAllIPs

For reference: 224.0.0.0/3 is two separate ranges, there were attempts in 2008 to repupurpose the "Class E" 240.0.0/4 network, which didn't pan out.  (blog: http://packetlife.net/blog/2010/oct/14/ipv4-exhaustion-what-about-class-e-addresses/).

Project Member

Comment 6 by sheriffbot@chromium.org, Aug 14

Cc: nhar...@chromium.org
Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
Thanks for the followup!  Closing this bug, per comment #5.
Project Member

Comment 8 by bugdroid1@chromium.org, Aug 16

The following revision refers to this bug:
  https://chromium.googlesource.com/chromium/src.git/+/d30507ca02b0c3ec59d8f9a8551de85a4f15a65e

commit d30507ca02b0c3ec59d8f9a8551de85a4f15a65e
Author: Nick Harper <nharper@chromium.org>
Date: Thu Aug 16 20:24:31 2018

Fix documentation for Cast private IP addresses

The documentation referred to RFC4913, which has nothing to do with IP
addresses. RFC4193 appears to be the correct RFC to cite.

Bug:  873490 
Change-Id: I606f20af8027f252dcef90726032c7723f62d0de
Reviewed-on: https://chromium-review.googlesource.com/1174962
Reviewed-by: Derek Cheng <imcheng@chromium.org>
Reviewed-by: Pavol Marko <pmarko@chromium.org>
Commit-Queue: Nick Harper <nharper@chromium.org>
Cr-Commit-Position: refs/heads/master@{#583793}
[modify] https://crrev.com/d30507ca02b0c3ec59d8f9a8551de85a4f15a65e/chrome/browser/flag_descriptions.cc
[modify] https://crrev.com/d30507ca02b0c3ec59d8f9a8551de85a4f15a65e/chrome/browser/media/router/media_router_feature.h
[modify] https://crrev.com/d30507ca02b0c3ec59d8f9a8551de85a4f15a65e/components/policy/resources/policy_templates.json

Sign in to add a comment