Le Dimanche 14 Mai 2006 17:44, vous avez écrit :
El 13/05/2006, a las 12:14, Rémi Denis-Courmont escribió:
There are possibly more troublesome issues:
1/ how to handle UDP, which is also supported by getaddrinfo(), and
has more varied usages (not just socket() then connect())?
but this
Hi,
RFC3879 deprecates site-local unicast addrresses. However it does not say
anything about site-local multicast addresses. Are they deprecated as well?
Most of the arguments for deprecation of site-local unicasts seem to apply for
site-local multicast too.
thanks
-prasad
RFC 3879:
Prasad,
On May 15, 2006, at 8:19 AM, ext Prasad Deshpande wrote:
Hi,
RFC3879 deprecates site-local unicast addrresses. However it does
not say anything about site-local multicast addresses. Are they
deprecated as well? Most of the arguments for deprecation of site-
local unicasts seem
Thanks. Me too. Sounds good.
Bert
-Original Message-
From: James Kempf [mailto:[EMAIL PROTECTED]
Sent: Monday, May 15, 2006 11:51 AM
To: Soohong Daniel Park; Manfredi, Albert E; Erik Nordmark
Cc: IPv6 WG; Jeff Mandin; Riegel, Maximilian; [EMAIL PROTECTED]
Subject: Re: WG Review:
Bernie Volz (volz) wrote:
It seems to me that having some process identified with a endpoint
(socket) has value. Yes, it may not be the actual process now using the
endpoint, but it still provides some meaningful information (such as the
process that originally created the endpoint).
Even
Obviously that is less than desirable, but just because some platforms
may be unable to provide useful information doesn't mean we just
deprecate it for all. Implementers of SNMP agents for this MIB will thus
need to decide whether they return a value for this item or not, and if
they do what
