Dave Thaler wrote:
Whenever any IPv4 packet is to be forwarded out an interface
whose MTU is smaller than the size of the packet, and the Dont
Fragment bit is set, the ARP proxy drops the packet and sends
a Fragmentation Needed message back to the source.
Similarly, whenever any IPv6 packet is t
On Tue, 15 Feb 2005, Dave Thaler wrote:
Proposed replacement text:
An implementation MUST have some means of preventing loops.
Loop prevention SHOULD be done by having the proxy implement the
Spanning Tree Algorithm and Protocol as defined in [BRIDGE] on all
proxy interfaces, as described below.
Is
On Tue, 15 Feb 2005, Erik Nordmark wrote:
So I'd suggest adding a sentence at the start of the second paragraph:
This specification has no explicit support for hosts to perform
inbound load balancing.
and rewording the rest to start with
Routers can perform inbound load bala
Issue page:
http://www.icir.org/dthaler/NDProxyIssues.htm#Issue%2022
Section 4.1 stated no ICMP errors are sent:
OLD: In particular, the IPv4 TTL or IPv6 Hop Limit is not
updated, and no ICMP errors are sent as a result of attempting
this forwarding.
and
OLD: Again the IPv4 TTL or IPv6 Hop Lim
123456789012345678901234567890123456789012345678901234567890123456789012
34567890
Three editorial suggestions from Ralph Droms (no further discussion as
yet):
#1
> My understanding is that NDproxy is intended for use between media
that
> cannot be bridged at the link-layer, and which, presumably,
Summary:
Requirements section says removal of a proxy should not adversely
disrupt the network. However, removing a proxy can break
connectivity that previously went through the proxy. Hence
the document is not self-consistent.
Discussion so far:
http://www.icir.org/dthaler/NDProxyIssues.htm#Is
Summary (from Erik Nordmark):
> I still think the document should say "MUST prevent loops;
> SHOULD run IEEE 802.1D to prevent loops" and then talk about
> cases when the protocol is not needed. The one example we have
> is the case of PPP (e.g. to a GGSN) where the probability of a
> loop would
The ND Proxy Issues page at
http://www.icir.org/dthaler/NDProxyIssues.htm
has been updated with the new issues raised (16 through 22), as well as
the comments received on each issue.
Issue 19 (Experimental vs Information) is already closed as noted below,
and does not affect the text.
For the r
Pekka Savola wrote:
Inbound load balancing - Nodes with replicated interfaces may want
to load balance the reception of incoming packets across
multiple network interfaces on the same link. Such nodes
have multiple link-layer addresses assigned to the same
On Tue, 15 Feb 2005, Soliman, Hesham wrote:
> This does not solve my wording issue. The paragraph just describes
> how _routers_ perform inbound load balancing. How about hosts which
> don't send RAs?
=> What do you suggest?
The paragraph now reads:
Inbound load balancing - Nodes with replic
> On Thu, 10 Feb 2005, Soliman, Hesham wrote:
> [lifetimes which decrement in real time]
> > > > > ==> AFAIK, the first option has not been implemented; I've
> > > > > at least not seen
> > > > > in done. Therefore unless someone shows that there are two
> > > > > implementations
> > > > >
On Thu, 10 Feb 2005, Soliman, Hesham wrote:
[lifetimes which decrement in real time]
> > > ==> AFAIK, the first option has not been implemented; I've
> > > at least not seen
> > > in done. Therefore unless someone shows that there are two
> > > implementations
> > > of this, this must be removed.
A New Internet-Draft is available from the on-line Internet-Drafts directories.
This draft is a work item of the IP Version 6 Working Group Working Group of
the IETF.
Title : Optimistic Duplicate Address Detection for IPv6
Author(s) : N. Moore
Filename
13 matches
Mail list logo
