2011/5/24, Ole Troan <[email protected]>: > > I would suggest incorporating the motivational parts of this document into > stateless-4v6-motivation
If we are supposed to converge these two drafts, the below is my proposal to reorganize the draft 1. Introduction 2. Operational Motivations Analysis 2.1 Improving Network Efficiency Note: This section states the benefits for off-loading traffic processing, e.g. reduction of logging information, efficient transmission of data packages, etc.. 2.1.1 NAT Logging Consideration 2.1.2 Avoiding Centralized Traffic Bottleneck 2.1.3 Optimizing Encap/Decap and Translation 2.1.4 xxxxx 2.2 Simplifying Network Maintenance Note: This section states the consideration for reducing subsequent efforts of network maintenance. 2.2.1 High Availability(HA) Consideration 2.2.2 Relief Qualification Procedures 2.2.3 xxxxx 2.3 Decreasing Transition costs Note: This section makes costs comparison analysis. 2.3.1 Transition Costs Consideration 2.4 Facilitating Service Evolution Note: This section states the cooperation between stateless 4via6 and service provisioning, e.g. the subsection "Implicit Host Identification" and "No Organizational Impact" in draft-operators-softwire-stateless-4v6-motivation-01. 2.4.1 xxxx 2.4.2 xxxx 3 Conclusions Note: I suggest to give the explicit conclusion, which approach is preferred and which has high-priority considering particular demands from operators. > and the stateless issues part of the draft into draft-dec-stateless-4v6-01 I support this idea. _______________________________________________ Softwires mailing list [email protected] https://www.ietf.org/mailman/listinfo/softwires
