Hello,
Alexandru Petrescu alexandru.petre...@gmail.com writes:
I am for adopting this draft as WG document.
+1
IETF IPv6 working group mailing list
ipv6@ietf.org
Administrative Requests:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I did think the verification problem that Heikki mentioned is
important and can happen in other protocols so I might fix the
wording to focus on the problem.
Certificates with IP addresses are sold and used, so I would not be
surprised if
Hi Fred,
see inline.
Gabi
- Original Message
From: Templin, Fred L fred.l.temp...@boeing.com
To: Gabi Nakibly gnaki...@yahoo.com; v6ops v6...@ops.ietf.org
Cc: ipv6@ietf.org; sec...@ietf.org
Sent: Tuesday, September 1, 2009 6:49:56 PM
Subject: RE: Routing loop attacks using IPv6
Gabi,
-Original Message-
From: Gabi Nakibly [mailto:gnaki...@yahoo.com]
Sent: Thursday, September 03, 2009 8:00 AM
To: Templin, Fred L; v6ops
Cc: ipv6@ietf.org; sec...@ietf.org
Subject: Re: Routing loop attacks using IPv6 tunnels
Hi Fred,
see inline.
Gabi
- Original
Hello,
Thank you for comments on the draft. I've been on a short vacation and
now the students are coming back, so I have a handful of excuses for not
having responded faster. O:-)
Brian E Carpenter wrote:
2.2. Autoconfiguration for Global Scope
This usually means that the next hop
Hi M. Bagnulo,
I read draft-ietf-shim6-locator-pair-selection-04, and I feel that it
overlaps with on-going work on address selection in a critical way.
Also, SCTP, MPTCP and MIF would need something like this as well, and it
doesn't make sense to define it separately for everything.
Some
