![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
On Nov 14, 2009, at 4:08 AM, Michael Richardson wrote:
"Tim" == Tim Winter <wintert at acm.org> writes:Tim> My opinion is for Option 1. I think that the applicability Tim> statements are the right place to start pinning down Tim> interoperability w.r.t. OFs - as appropriate to each Tim> application space. This may also include interoperability Tim> between application spaces.I'm fine with that. The applicability statements will be the main anchorinto the standard, that's fine. My concern is that it appeared thatsome wanted to leave to do other industry "fora" to declare. As long asthere is an IETF standards track document that says what is what, then I'm happy.
Excellent. Issue resolved. Just note that applicability statements are part of our charter
and will be informational. Thanks. JP.
--] He who is tired of Weird Al is tired of life! | firewalls [ ] Michael Richardson, Sandelman Software Works, Ottawa, ON |net architect[ ] mcr at sandelman.ottawa.on.ca http://www.sandelman.ottawa.on.ca/ | device driver[ Kyoto Plus: watch the video <http://www.youtube.com/watch?v=kzx1ycLXQSE >then sign the petition. _______________________________________________ Roll mailing list Roll at ietf.org https://www.ietf.org/mailman/listinfo/roll