Seb, I finally got to revise and repost the document for a second pass. Thanks again for the feedback.
The changes ensuing from your comments have been recorded to be easily identifiable. I do have a question in the section that talks about deleting 6to4 tunnels to the router (p. 9, Step 3). Let me know if this specific step should also be replaced by the dladm subcommand. Some comments on your feedback are inline. Sebastien Roy wrote On 09/27/06 14:51,: > Raoul, > > > Excellent. This is a good start. Here is my feedback: > > I think it would help to introduce what IP tunneling is and what its > conceptual parts are so that the language used in the document can be more > clear and be made more explicit. For example, there is a conceptual > separation between a tunnel data-link and a tunnel IP interface which is > configured above that data-link. That conceptual separation is reflected in > the administrative model, in which the data-link is administered using > dladm, and the IP interface is administered using ifconfig. > ==> Steff has an AI to have an introductory chapter that will be placed in the new sysadmin guide that we are currently developing. The conceptual distinctions will be included in that intro chapter that serves as an overview of clearview in general. > Also, there is no tie-in with IPsec in here, and I think there needs to be. > This is especially important given the IPsec tunnel reform work that is > happening (are you in touch with the documentation writer for that > project?). The method of configuring IPsec policy for IP tunnels is being > significantly enhanced by that project, and IPsec VPNs is one of the primary > uses of IP tunneling. > ==> I have included a note that serves as a bridge to the IPsec topic. I mention there how IP tunnel and IPsec are associated features, and I point to the IPsec chapter for the more detailed information. I will coordinate with the IPsec writer regarding the changes in her doc that involves IP tunnel and the dladm command. Thanks! Raoul
