On Wed, 19 Mar 2003, Bound, Jim wrote:
- Node Reqs 3GPP services - Node Database Services - Node Requirements iSCSI/IP
Etc Etc.
The scope is to narrow currently.
Jim, I can see what you would like to do, but I don't agree that this is possible. It is not possible to document the requirements for all potential applications. And I don't want to start arguing about what the three most important applications are, if that's what you were thinking.
What we *can* do, however, is to list the "components" IPv6 as a reference for implementers, vendors, and customers. While it may be obvious to some folks what these components are, I believe this is an extremely useful exercise which will also help IPv6 deployment.
Also, we in this working group should be able to specify what the core components -- those which are always mandatory no matter what -- are. We are also documenting the optional features*. After a discussion on the mailing list we concluded that the MUST/SHOULD/MAY language is the best choice for this documentation. But by no means should this be taken to mean that an "optional" component is not absolutely necessary in a specific application. Clearly they can be, but I agree with Pekka that some judgment outside the IETF standards needs to be applied as well.
Jari *) Actually, only some optional components e.g. on sub-IP are listed. I disagree with this approach, I'd rather have all the optional components.
-------------------------------------------------------------------- IETF IPng Working Group Mailing List IPng Home Page: http://playground.sun.com/ipng FTP archive: ftp://playground.sun.com/pub/ipng Direct all administrative requests to [EMAIL PROTECTED] --------------------------------------------------------------------
