[anonsec] BYPASS OR PROTECT

[Nicolas Williams]

On Mon, Apr 16, 2007 at 01:22:10PM +0200, Julien Laganier wrote:
> Before I forward it to IESG, I need you to resubmit a 
> new version of the draft that passes all IDnits 
> checks:
> 
> <http://tools.ietf.org/tools/idnits/>
> 
> It currently has 4 errors:
> 
> - No 'Intended status' indicated
> 
> ==> Use "std" as category in the XML's <rfc> mark (e.g. 
> <rfc category="std" ipr="full3978" > )

OK.

> - Lack an IANA Considerations section
> 
> ==> If the document hasn't IANA considerations, include 
> an IANA cons section stating "This document has no 
> IANA considerations"

OK.

> - Bad Normative/Informative ref split causing downrefs.
> 
> ==> I think [I-D.ietf-btns-connection-latching], 
> [I-D.ietf-btns-prob-and-applic], 
> [I-D.ietf-kitten-gssapi-channel-bindings], and 
> [I-D.ietf-nfsv4-channel-bindings] are Informative 
> rather than Normative...

And I-D.ietf-nfsv4-channel-bindings has been replaced with
I-D.williams-on-channel-bindings.

OK.

> - Normative reference to obsolete RFCs (RFC 2408 and 
> RFC2409)
> 
> ==> Suggest removing them, or move to Informative?

Those should be informative, since they are only referenced in the
Introduction.  Similarly for RFC4306 (IKEv2).  The only normative
references left are to RFC2119 and RFC4301.

> Once those are taken care of, I'll forward the draft to 
> IESG.

I'll re-submit shortly.

Nico
--