> > > 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. > > Or will there soon be "mobile terminals" that have IP router > > functionality? > > I suspect it makes sense to very clearly restrict the > document to only > > be about terminals that have no router functionality. > > 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? > > thanks, > 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] > -------------------------------------------------------------------- > -------------------------------------------------------------------- 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] --------------------------------------------------------------------
