IBM Z Hardware and Operating Systems Ideas Portal
Hide about this portal
This is the public portal for all IBM Z Hardware and Operating System related offerings. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Search existing ideas
Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,
Post your ideas
Post an idea.
Get feedback from the IBM team and other customers to refine your idea.
Follow the idea through the IBM Ideas process.
Specific links you will want to bookmark for future use
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.
Thank you for submitting this Idea regarding underscores in URIs.
The toolkit has two URI inputs, one for the connection handle, and the second for the request handle, as seen below:
Connection URI: scheme "://" host
Request URI: "/" path "?" query "#" fragment
The second portion of the URI, used on the request handle, already supports underscores as unrestricted.
This first portion of the URI has more stringent requirements, in accordance with RFC3986:
The scheme must be either "http" or "https" (case insensitive).
The host is either an IPv4 address, an IPv6 address, or a registered DNS name. The toolkit does not guarantee support for other types of registered names at this time.
Each of these have their own character set rules in https://datatracker.ietf.org/doc/html/rfc3986#section-3.2.2. IPv4 must have only digits and "."; IPv6 can have hexadecimals, "[", "]", ":", and "."; and DNS names must adhere to:
> A registered name intended for lookup in the DNS uses the syntax
> defined in Section 3.5 of [RFC1034] and Section 2.1 of [RFC1123].
> Such a name consists of a sequence of domain labels separated by ".",
> each domain label starting and ending with an alphanumeric character
> and possibly also containing "-" characters.
And in https://datatracker.ietf.org/doc/html/rfc1034#section-3.5:
> The labels must follow the rules for ARPANET host names. They must
> start with a letter, end with a letter or digit, and have as interior
> characters only letters, digits, and hyphen. There are also some
> restrictions on the length. Labels must be 63 characters or less.
The standard does not officially support the usage of underscores in DNS names, and it is recommended that administrators adhere to DNS names that are part of the standard.
However, non-standard DNS names might be found in local networks or closed intranets, which would need a more relaxed set of rules. Would allowing a DNS name with underscores resolve the problems you are seeing with the URIs provided by your customer?