[bind10-dev] Convention for address+port: forget rough consenus, lets vote!

[Dave Hart]

On Wed, Aug 10, 2011 at 20:41, Tomasz Mrugalski <tomasz at isc.org> wrote:
> Of course interface name should be used only when it is really
> necessary. Assuming that currently leading option (Option 3 in doodle
> poll: IETF standards (RFC 2396 and RFC 2732): v4address:port and
> [v6address]:port) wins, we could use one of the following:
>
> 1. [ff02::1:2%eth0]:547
> 2. [ff02::1:2]:547%eth0
> 3. [ff02::1:2]:547 at eth0
> 4. [ff02::1:2 at eth0]:547
> 5. eth0/[ff02::1:2]:547
>
> 1. and 2. are based on notation used by OS X (and most BSDs, I think).

1. is also used by ntpd and friends for both input and output (output
for link/scope locals only):

C:\Users\davehart>ntpq -c "ifstats" [fe80::5dda:bd83:f979:6e03%20]
Keyid: 123
MD5 Password:
    interface name
 #  address/broadcast     drop flag ttl mc received sent
========================================================
  0 v4wildcard               D   89   0  0      0      0
    0.0.0.0:123
  1 v6wildcard               D   81   0  0      0      6
    [::]:123
  2 Loopback Pseudo-Interfac .   15   0  0      1      0
    [::1]:123
  3 Loopback Pseudo-Interfac .   15   0  0      0      0
    127.0.0.1:123
  4 Clear4G                  .   51   0  1      0      0
    [fe80::5dda:bd83:f979:6e03%20]:123
  5 Clear4G                  .   59   0  1   3586   3733
    184.78.246.47:123
  6 he6in4                   .   51   0  1   9576   9658
    [2001:470:a:4f3::2]:123
  7 he6in4                   .   51   0  1      0      0
    [fe80::c8b5:a7b6:b4e3:ee08%21]:123
  8 Local Area Connection* 1 .    1   0  0      0      0
    [2002:b84e:f62f::b84e:f62f]:123

Cheers,
Dave Hart