Document: draft-ietf-multi6-architecture-03.txt Review: Michael A. Patton Date: 2 februari 2005 Summary: This draft is ready for publication as an Informational RFC I had two extremely minor comments and a few typos, but on the whole I found it fairly well explained and comprehensive. I do have to disclaim that as one of the group that argued for a separation of locators and endpoint IDs in the initial IPv6 definition, I'm not unbiased in this area. At the end of Section 6.3.4 it notes that "This approach implies that the active end of a communication needs to cycle through all of its associated locators as source addresses until it receives a response or exhausts its locator set." However, it's worse than that, it needs to try the full cross product of all of its locators as source as well as all of the remote's locators as destination. Of the MxN combinations, there may only be one that works. I would suggest that publication of this document and of draft-ietf-multi6-things-to-think-about should be tied together. I also note that this document cites an old version of that other document. Additionally, I expect that this needs to be tied to the security one based on the security section. Typos: ------ Section 2 (under Endpoint Identity Protocol Stack Element): "E ndpoint" => "Endpoint" Section 2 (under Multi-Homed Site): "one transit providers" => "one transit provider" Section 3: "particularl" => "particular" Section 4: "further consideration also include" => "further considerations also include" Section 5.1: "Neither the local or the remote host" => "Neither the local nor the remote host" Section 5.3: "ISP B' address prefix" => "ISP B's address prefix" Section 5.3: "ISP A vs. ISP B" => "ISP A vs. ISP B" Section 6: "pass the reminder of the PDU" => "pass the remainder of the PDU" Section 6.2: "represents a approach" => "represent an approach" Section 6.2: "in mosts contexts" => "in most contexts" Section 6.2: "that a the" => "that the" Section 6.2: "discivered" => "discovered" Section 6.2: "an open question as how" => "an open question how" Section 6.3.2: "how is this interaction is to be" => "how this interaction is to be"