In your letter dated Wed, 21 Apr 2010 16:33:03 +1200 you wrote:
By contrast, a source host
never has this problem, because it knows by construction when a flow
ends (chances are, flow == socket).
I'm wondering about the 'never' part. What if an application uses sendto()
to communicate over UDP
Le 20 avr. 2010 à 19:35, james woodyatt a écrit :
On Apr 20, 2010, at 09:56, Rémi Després wrote:
Using the experimental status seems to me confusing (and why two numbers
instead of one?)
There are two numbers reserved for protocols, and I was plagued by the
hobgoblins of consistency. I
Hi Brian,
I wonder what you think of what I answered to James on another discussion
thread.
Regards,
RD
Début du message réexpédié :
De : Rémi Després remi.desp...@free.fr
Date : 21 avril 2010 10:43:55 HAEC
À : james woodyatt j...@apple.com
Cc : 6man 6man ipv6@ietf.org
Objet : Rép :
Hi Suresh,
RFC 4861 Statement:- 7.2.1.Interface Initialization
“When a multicast-capable interface becomes enabled, the node MUST join the
all-nodes multicast address on that interface, as well as the solicited-
node multicast address corresponding to each of the IP addresses assigned
to the
No answer from anywhere, even the State of Confusion...
B. R.
Tina
http://tinatsou.weebly.com/contact.html
- Original Message -
From: Tina TSOU
To: ipv6@ietf.org ; v6...@ops.ietf.org ; Bob Hinden ; Dan Romascanu ;
fen...@fenron.com ; fen...@gmail.com ; dtha...@microsoft.com ;
Niviya,
When a multicast-capable interface becomes enabled, the node MUST join the
all-nodes multicast address on that interface, as well as the solicited-
node multicast address corresponding to each of the IP addresses assigned to
the interface.
Any idea What does this statement
[sorry if you get duplicates, replying from an address that actually
*works* this time]
2010/4/19 Tina TSOU t...@huawei.com:
In RFC 4293,
- ipAddressTable is described as writable, this table uses address
as index, but the critical information for configuring address, the
address prefix
2010/4/19 Tina TSOU t...@huawei.com:
In RFC 4293,
- ipAddressTable is described as writable, this table uses address
as index, but the critical information for configuring address, the
address prefix ipAddressPrefix node is read-only. It seems
contradict to me.
Worse, the whole
we didn't pay enough attention is a very kind way to put it. The entire SNMP
exercise was about monitoring; those like me who tried to make things writable
pushed rocks uphill politically. That, and the experience of trying to make
event triggered management rather than poll-driven management,
On 2010-04-21 19:11, Philip Homburg wrote:
In your letter dated Wed, 21 Apr 2010 16:33:03 +1200 you wrote:
By contrast, a source host
never has this problem, because it knows by construction when a flow
ends (chances are, flow == socket).
I'm wondering about the 'never' part. What if an
On 2010-04-21 20:50, Rémi Després wrote:
Hi Brian,
I wonder what you think of what I answered to James on another discussion
thread.
I agree. I think that particular SHOULD in the RFC is an error. It SHOULD
have said something like:
The source node MUST select new Flow Label values by a
Hi,
Sheng and I would like to continue our attempt to make the flow label
useful. The discussions in Anaheim and on this list have been very
stimulating. I think we need to simplify the change proposed in
draft-carpenter-6man-flow-update-02 even more after the recent
discussions, while
Hi,
Sheng and I would like to continue our attempt to make the flow label
useful. The discussions in Anaheim and on this list have been very
stimulating. I think we need to simplify the change proposed in
draft-carpenter-6man-flow-update-02 even more after the recent
discussions, while
13 matches
Mail list logo
