Re: IESG feedback on core drafts.

["Steven M. Bellovin" <smb%research.att.com@localhost>]

In message <200303170019.h2H0J0aj014266%thunk.east.sun.com@localhost>, Bill Sommerfeld wr
ites:
>> >So, I'm wondering if it might make more sense to have a single set of
>> >security considerations in the -arch draft, with pointers from the
>> >other three documents.  Like most things security related, they cut
>> >across functional areas, and I really don't want to waste time
>> >trying to get all the hairs perfectly split.
>> 
>> Always a reasonable option.  Will such a document appear in finite 
>> time?  The IESG is not fond of approving documents that say "see the 
>> following non-existent RFC for security considerations" -- but has 
>> often approved documents that point to existing documents for that 
>> information.
>
>The -arch draft, draft-ietf-secsh-architecture-13.txt,
>is currently part of the core drafts hairball before the IESG at this
>moment.
>

Right, but currently the security considerations information is split 
across many different documents.  You'd have to collect it in that one 
place -- which would be a good idea.

		--Steve Bellovin, http://www.research.att.com/~smb (me)
		http://www.wilyhacker.com (2nd edition of "Firewalls" book)