FWIW, I've never seen netstat (or ifconfig, etc) display IPv6 addresses inside [] on either UNIX or Linux, and that probably won't change anytime soon. I thought RFC 3986 only applied to URLs and the like, not command output.
-Brian Dave Thaler wrote: > I'll note that the netstat output below is arguably non-standard since it > includes > port numbers without encosing the address in []. > (The arguable part is whether [] is limited to URLs or applies in general) > > Windows would display them as [::]:22 etc. > > Perhaps this draft should be extended to cover text representation > of IPv6 addresses + ports, and discuss this issue? > > -Dave > ________________________________________ > From: Brian Haley [[email protected]] > Sent: Thursday, May 14, 2009 11:31 AM > To: IPv6 WG Mailing List > Cc: Dave Thaler; Brian Haberman > Subject: Re: Review requested: draft-kawamura-ipv6-text-representation-02 > > Dave Thaler wrote: >> I read and I agree with the document except for Appendix A. >> >> For one, I disagree that v4 mapped addresses are not recommended. >> They're commonly used for sockets that support both IPv4 and IPv6. > > I would agree with Dave. If you ssh to any recent Linux system over IPv4 > you'll > see a mapped address since sshd only opens an IPv6 socket: > > # netstat -an | grep 22 > tcp6 0 0 :::22 :::* LISTEN > tcp6 0 0 ::ffff:10.202.1.26:22 ::ffff:10.0.0.39:49571 > ESTABLISHED > > Some OSes hide the ::ffff:, some don't, but it's not a security or portability > issue. > > -Brian -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
