netdev
[Top] [All Lists]

Re: sin6_scope_id

To: lordbeatnik <lordbeatnik@xxxxxxxxxxxxxx>
Subject: Re: sin6_scope_id
From: Andi Kleen <ak@xxxxxx>
Date: Thu, 13 Jan 2000 01:47:14 +0100
Cc: netdev@xxxxxxxxxxx
In-reply-to: <200001122348.PAA20112@xxxxxxxxxxxxxxxx>; from lordbeatnik on Thu, Jan 13, 2000 at 12:51:29AM +0100
References: <200001122348.PAA20112@xxxxxxxxxxxxxxxx>
Sender: owner-netdev@xxxxxxxxxxx
On Thu, Jan 13, 2000 at 12:51:29AM +0100, lordbeatnik wrote:
> kuznet@xxxxxxxxxxxxx wrote:
> >Hello!
> >
> >> Everyone has to support sin6_scope_id.
> >
> >Yes, Sir! Are we in the army now? 8)
> >
> >
> >Let me to cite the only intelligible argument for sin6_scope_id
> >(your one, right?) to show people, who did not listen ipng,
> >style of IPng WG discussions, resulting in such decisions:
> 
> well, it's not a very good reason, (there are other ways of getting around 
> it), but for telling which interface a multicast packet came from if you 
> bound your multicast socket to ifindex 0 and as another way to tell what 
> interface to send out a multicast packet.
> 
> but then, as I said earlier, this can also be done by setting sockets to 
> specific ifindexes when joining a multicast group.
> 
> It's not much, but it's something to think about.

Or by using IPV6_PKTINFO

Anyways, there is a unused 16bit field in the linux sockaddr_ipv6,
so adding it later for source code compatibility is always possible.

-Andi
-- 
This is like TV. I don't like TV.

<Prev in Thread] Current Thread [Next in Thread>