Catching up on email... I will go through the rest of last weeks responses over the next day or so.
> -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of > Erik Nordmark > Sent: Monday, January 24, 2005 9:26 AM > To: Brian E Carpenter > Cc: Thomas Narten; Margaret Wasserman; Brian Haberman; IPv6 > Subject: Re: Request to Advance: <draft-ietf-ipv6-ndproxy-00.txt> [RESEND] > > Brian E Carpenter wrote: > > > First, lets keep in mind that this is an Informational document. > > > > I wonder whether Experimental wouldn't send a clearer signal > > that there is some doubt about the viability of the solution. > > That would be better than informational. I have no objection. > But 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. I agree. > The one example we have is the case of PPP (e.g. > to a GGSN) where the probability of a loop would be very small, so in > that particular case there is no need for 802.1D (and there might be > other examples, but the 802.11 scenario in the document isn't one of > them). > > > I can see how this could be very useful in certain types of > > network environment, and publishing as Experimental will allow > > people to share experience and try to fix the open questions. > > ok > > > Since the deployment future of SEND is unknown, I don't think > > it's appropriate to block this work because of SEND. Right. As Brian pointed out, proxy ND is already part of RFC 2461, and it's already PS. It's also still in draft-ietf-ipv6-2461bis-01.txt which is targeted for DS. The fact that SEND doesn't yet support proxy ND is not specific to this specification, it's something for SEND to solve. I'll respond to other points in subsequent email. -Dave > Yes, but at least the document should be internally inconsistent and not > claim in section 3 that working with SeND is a requirement, even though > it doesn't work with SeND. > > Erik > > -------------------------------------------------------------------- > IETF IPv6 working group mailing list > [email protected] > Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 > -------------------------------------------------------------------- -------------------------------------------------------------------- IETF IPv6 working group mailing list [email protected] Administrative Requests: https://www1.ietf.org/mailman/listinfo/ipv6 --------------------------------------------------------------------
