Pekka wrote: >You apparently consider SHOULD as almost a MUST.
>I support SHOULD in this case; it's meant for manually configured >nodes, really. I certainly want to be able to manually configure my >systems _if I want to_. >You've convincing reasons why you don't want to implement that -- always >use autoconfiguration. (I suspect you're dealing with small devices >which cannot really be "configured" anyway). It's okay. You are correct, as I interpret things, SHOULD implys you better have a good reason not to do something, and be able to back it up. I typically interrpret shoulds as almost a must is because sooner or later we'll get an RFP based on this type of document, and anything marked MUST and SHOULD gets marked as MUST in the RFP. Happens all the time. MAY on the otherhand is vendor specific, if you want to do it, or your customers desire it, go right ahead. It doesn't stop manually configured nodes the ability to manually configure. Adam Machalek -------------------------------------------------------------------- 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] --------------------------------------------------------------------
