Re: [secdir] secdir review of draft-yourtchenko-cisco-ies-09

[Andrew Yourtchenko <[e-mail]>]

Hello Charlie,

I've published the 
http://tools.ietf.org/html/draft-yourtchenko-cisco-ies-10 today, which 
hopefully took care of the first part of the comments.

The formatting in the Appendix A is a result of xml2rfc way of treating 
the longer URLs. Unfortunately I can not control it, so could not take 
care of it.

On the other hand, hopefully the unusual style of truncation makes it 
understandable that these URLs need concatenating from the pieces, and 
this might be taken care of by the potential users of the XML.

Thanks a lot for the review !

--a

On Sat, 25 Jan 2014, Charlie Kaufman wrote:

> I have reviewed this document as part of the security directorate's ongoing effort to review all IETF documents being processed by the IESG.  These comments were written primarily for the benefit of the security area directors.  Document editors and WG chairs should treat these comments just like any other last call comments.
>
> This document is a mechanism to bring an IANA registry of log event types up to date to correspond with existing practice based on updates to the protocol defined in RFC3954. There are no security considerations other than vague concerns over what a buggy existing implementations might do if they see new event types that they don't recognize. This should not be controversial.
>
> Formatting nits:
>
> At the bottom of page 2 and the top of page 3, there are question marks that seem to have a pre-pended space that looks out of place, but it may have been required by some formatting requirement around the bracketed reference that precedes it.
>
> The formatter that translated the XML in appendix A into text for the RFC seems to have strange taste in where to place line breaks. For example, in the middle of page 13, there appears:
>
> <reference>
> http://www
> .cisco.com
> /en/US/pro
> ducts/hw/s
> witches/ps
> 700/products_configuration_example...
>
> 	--Charlie
>