Hi Phil, > > > BTW: Does 1) include the ability to run e.g. Java applets or > > > other downloadable code? > > > > I think we would clasify it as closed, no applets or > > downloadable code. > > Hmmm. I think you've excluded a large number (the majority) of the > kinds of devices that you'd like to be giving guidance on.
There will be many different types of devices, some will support downloadable code, some will not. Currently, I don't know if the majority will be one sort or another. Some folks will want bells & wistles, some won't. I prefer to turn java off when I browse the net ... > > Right now, in 3GPP specifications, there is not this > > possibility. The market might do something else at some point > > (my visibility isn't exactly clear on this point), but it has > > always been my intention that terminals with IP router > > functionality should > > have seperate requirements, something I think most of the > > authors are interested in specifying (in a seperate draft) > > after this draft is done. > > Hmmm (again). I guess I'm wondering what is to prevent the > terminal from having a router in it. 3gpp has agreed to update > the spec to assign a prefix, no? What's to keep someone from > running routing protocols over the link? Again, we have never said that this won't happen, there are then quite a few additional issues to be tackled. We're seperating the two functionalities. For example, I don't think a general host requirement document should address routing either. John -------------------------------------------------------------------- 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] --------------------------------------------------------------------
