Sorry I wasn't clear.<div><br></div><div>What I mean is the "content" of the security considerations needs to be in one place. Each document will have its security considerations section, but they would all point to one location, instead of two as the do now, eg in Tables:<div>
<br></div><div><span class="Apple-style-span" style="font-family: Times; font-size: 16px; "><pre class="newpage" style="font-size: 1em; margin-top: 0px; margin-bottom: 0px; page-break-before: always; "><span class="h2" style="line-height: 0pt; display: inline; white-space: pre; font-family: monospace; font-weight: bold; "><h2 style="line-height: 0pt; display: inline; white-space: pre; font-family: monospace; font-weight: bold; ">
<a name="section-6"><span class="Apple-style-span" style="font-size: small;">6</span></a><span class="Apple-style-span" style="font-size: small;">. Security Considerations</span></h2></span><span class="Apple-style-span" style="font-size: small;">
The security issues associated with this work are discussed in
[</span><a href="http://tools.ietf.org/html/draft-ietf-idnabis-tables-04#ref-IDNA2008-rationale" title=""Internationalized Domain Names for Applications (IDNA): Background, Explanation, and Rationale""><span class="Apple-style-span" style="font-size: small;">IDNA2008-rationale</span></a><span class="Apple-style-span" style="font-size: small;">] and [</span><a href="http://tools.ietf.org/html/draft-ietf-idnabis-tables-04#ref-IDNA2008-protocol" title=""Internationalizing Domain Names in Applications (IDNA): Protocol""><span class="Apple-style-span" style="font-size: small;">IDNA2008-protocol</span></a><span class="Apple-style-span" style="font-size: small;">].</span>
</pre><div><span class="Apple-style-span" style="font-family: -webkit-monospace; white-space: pre;"><br></span></div></span>Mark<br>
<br><br><div class="gmail_quote">On Wed, Nov 19, 2008 at 18:44, Vint Cerf <span dir="ltr"><<a href="mailto:vint@google.com">vint@google.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">
turns out that IETF procedures require security considerations for all RFCs.<div><br></div><div>v</div><div><br><div> <span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-align:auto;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="border-collapse:separate;color:rgb(0, 0, 0);font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:normal;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><div>
<div>NOTE NEW BUSINESS ADDRESS AND PHONE</div><div>Vint Cerf</div><div>Google</div><div>1818 Library Street, Suite 400</div><div>Reston, VA 20190</div><div>202-370-5637</div><div><a href="mailto:vint@google.com" target="_blank">vint@google.com</a></div>
<div><br></div></div></span><br></span><br></span></span></span> </div><br><div><div><div></div><div class="Wj3C7c"><div>On Nov 19, 2008, at 9:08 PM, Mark Davis wrote:</div><br></div></div><blockquote type="cite"><div><div>
</div><div class="Wj3C7c"><span style="font-family:Garamond"><h1 style="font-size:18pt">Security Considerations</h1><div style="margin-top:0px;margin-bottom:0px">D4. Security Considerations<div style="margin-top:0px;margin-bottom:0px">
R12. Security Considerations<br><div style="margin-top:0px;margin-bottom:0px"><br></div><div style="margin-top:0px;margin-bottom:0px">I think it is a really bad idea to split the Security Considerations between Defs and Rationale. There doesn't seem to be any particular reason for the split. They should all be in one place, preferably in Protocol, since that is the core document.</div>
<div><br></div></div></div></span>Mark<br></div></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px">_______________________________________________</div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px">
Idna-update mailing list</div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px"><a href="mailto:Idna-update@alvestrand.no" target="_blank">Idna-update@alvestrand.no</a></div><div style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px">
<a href="http://www.alvestrand.no/mailman/listinfo/idna-update" target="_blank">http://www.alvestrand.no/mailman/listinfo/idna-update</a></div> </blockquote></div><br></div></div></blockquote></div><br></div></div>