<br><br><div class="gmail_quote">2009/4/11 Patrik Fältström <span dir="ltr"><<a href="mailto:patrik@frobbit.se">patrik@frobbit.se</a>></span><br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
A. Should we defined MVALID?<br>
B. What should the general rule be that define it (we can have codepoints in Exceptions as before)?</blockquote><div><br>JFC and I are on Easter vacations so I cannot ask him to confirm, but I feel you are converging. Not the same vision yet, but nearer wavelength. My personnal suggestion would be to consider the DN layers by themselves (DNS, application, user). Then the way they articulate in the network+application+usage architecture. Then the way and where to achieve that kind of articulations. Your part would then be this last issue. Modulations would then be much easier to analyse, document and protect. <br>
<br>I know I am French: I need some methodology. Sorry for that, but I feel it helps. I feel A, M, U labels concepts should be put in a table in regards of DN layers and the services performed at this layers. Because various usages, inter-applications, and security concerns are to hook in the proprer way to the linguistic naming pile. In discussing such a table, we might get to better definitions and mutual understanding.<br>
<br>Rémy Renardin<br><br></div></div><br>